# Trigger gateway event on seconds

**URL:** <https://forum.inductiveautomation.com/t/trigger-gateway-event-on-seconds/113653>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [January 30, 2026, 7:09am UTC](https://forum.inductiveautomation.com/t/trigger-gateway-event-on-seconds/113653 "2026-01-30T07:09:39Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\
**Post date:** [January 30, 2026, 11:30am UTC](https://forum.inductiveautomation.com/t/trigger-gateway-event-on-seconds/113653/8 "2026-01-30T11:30:12Z")

</div>

> [@Gateway Script Only at 4pm](https://forum.inductiveautomation.com/t/gateway-script-only-at-4pm/19979/8):
>
> Bad. If the gateway experiences any heavy load at 4pm, this expression can miss the event. Especially if using fixed delay. If using fixed period, and the event that normally falls a 3:59:59 is slightly delayed, this can fire twice in a row. The chance is low, so you wouldn't be likely to see either problem often, but it would happen. I would use something like this in a project script module: from java.util import Date lastTrigPath = '[default]some/path/to/datetime/tag' # Simple functio…

---

_[View the full topic](https://forum.inductiveautomation.com/t/trigger-gateway-event-on-seconds/113653)._