# Vision Alarm Status Table, acknowledge button uses timestamp from client computer

**URL:** <https://forum.inductiveautomation.com/t/vision-alarm-status-table-acknowledge-button-uses-timestamp-from-client-computer/102208>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [February 11, 2025, 8:55pm UTC](https://forum.inductiveautomation.com/t/vision-alarm-status-table-acknowledge-button-uses-timestamp-from-client-computer/102208 "2025-02-11T20:55:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eric\_G](https://avatars.discourse-cdn.com/v4/letter/e/258eb7/32.png) [@Eric\_G](https://forum.inductiveautomation.com/u/Eric_G)\
**Post date:** [February 11, 2025, 8:55pm UTC](https://forum.inductiveautomation.com/t/vision-alarm-status-table-acknowledge-button-uses-timestamp-from-client-computer/102208/1 "2025-02-11T20:55:02Z")

</div>

v8.1.42

Clicking the Acknowledge button on an Alarm Status Table component generates a row in the alarm\_events table where eventtype=2 and eventtime is from the **client** computer's clock.

However, the record with eventtype=0 has an eventtime from the **gateway's** clock.

This makes computing the time between the alarm being active and getting acknowledged a dubious adventure.

Is there a way to configure or modify this behavior?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 11, 2025, 9:12pm UTC](https://forum.inductiveautomation.com/t/vision-alarm-status-table-acknowledge-button-uses-timestamp-from-client-computer/102208/2 "2025-02-11T21:12:37Z")

</div>

Not that I know of.

Vision is pretty dependent on close clock synchronization for many reasons, including proper operation of real-time charts.