My Automation rule is set for 11am but went off at 11:34, why?

[Connor_McCormick]

My automation is set to go off at 11AM

But for whatever reason it went off at 11:34 instead

Why did this happen? Any way I can fix it? @mallika

To make this searchable: Automation runs at wrong time. Incorrect trigger for automation. Reminder happens at a different time.

Thank you

[jeo]

@Connor_McCormick a brief history of this request

---

(2018-11-30)

@Himanshu

Triggers should fire within few mins at most. There have been some issues where we have seen very high latency and we are making changes to fix them that should go live in a day or two.

---

(2019-08-07)

@Raul_San_N.H

automations work great but there is a long delay from the moment a row is changed to the moment the automation runs

---

(2019-11-18)

@BenLee

Currently automations will hit the queue when server time allows. Sometimes there may be a delay. This is something we will revisit later as we work on a few other items in the system. Automations aren’t guaranteed to run at exactly that time.

---

(2019-11-20)

@Paul_Danyliuk

consider adding “real-time automations” somewhere. Maybe enterprise plan, or a team plan, but I totally see how for some people it may be a crucial thing, something worth paying an extra for.

---

(2020-01-25)

@Paul_Danyliuk

P.S. While having automation is nice, it still doesn’t feel that reliable to me. Usually automation triggers are delayed, and once it was as much as half a day for me. Adding high precision automation triggers and/or triggers that fire immediately when user data changes (i.e. fire on the client side and not the server side — like pressing a button right after a value is changed) would make this a killer feature, but so far it’s too flaky IMO to totally rely upon.