Gateway Timer Event Script Last Execution Exceeds Rate

We have a number of Gateway Timer Event Scripts that run on our Gateway, across several projects. It was noticed that the Last Execution value exceeds the Rate (or Delay) for the Event. For example, a number of Timer Events that have delays configured of 30 seconds are actually running approximately every minute.

There seem to be some that are taking a long time to complete (several times the delay value). Does the Gateway wait until an event completes before triggering it again, or are those instances queued or something other than waiting?

Will the long running event scripts have any affect on the other events triggering. Notice that the highlighted events all have delay values of 30 seconds and duration times of less than a second. So if the long running event scripts aren’t affecting these from trigging on time (at 30 seconds after the last trigger/completion), what could be causing these to take a minute to trigger again?

Thanks!

Yes, always. And if in delay mode, the delay starts when the event ends.

Consider using a logger to mark the start and end of suspicious events.