I am reading the page Best practices for high performance apps and noticed this warning:
When triggers enter the queue faster than they exit, the queue builds up. Sustained trigger queue buildup causes app latency and, in some cases, dropped trigger events.
Is it known exactly in what cases trigger events can be dropped?
Hi Evan,
The best practices page is the right reference for how to approach this, and following it will keep you well clear of dropped trigger events.
In practice, the only things that could realistically build a trigger queue up far enough to drop trigger events are timer triggers on very low intervals, around 1 second, and utilizing a large amount of high frequency machine triggers. The risk compounds when either one calls a long-running action, most often a connector function. A machine outputting at 1Hz driving a trigger that runs a 5 second connector function is the typical example, since events arrive faster than they can be processed.
If you are seeing this in one of your apps, feel free to share the trigger setup + what it calls and Iād be happy to take a look.
Best,
Aidan
Thank you, Aidan, for your response!
So, just to clarify, what causes triggers to be dropped is when the number in the queue exceeds a certain size? Is there any quantification of what it takes to do that? I understand the recommendations to avoid it, I just want to understand what actually causes it.
I think it is written here.