Have you ever faced an issue where your workflows or triggers seem to malfunction, slowing down your app’s performance? That’s when Loop Lockouts come into play. As someone who has encountered this challenge firsthand, I can tell you how frustrating it is when triggers keep firing repeatedly, causing a system slowdown. In this article, I’ll explain what Loop Lockouts are, how they happen, and what you can do to fix them.
What Are Loop Lockouts?
Loop Lockouts happen when two triggers feed into each other, or a trigger keeps firing for the same contact, creating an infinite loop of actions. These loops take up valuable server resources, which results in slower performance for all users. To avoid this, the system now detects potential loops and locks the triggers that may cause them.
When Do Loop Lockouts Occur?
A Loop Lockout will trigger when a workflow, trigger, or campaign exceeds 50 starts or executions for the same contact within 30 minutes. This is an automatic safeguard to ensure your system doesn’t overuse resources or slow down.
Example:
- If a trigger fires 50 times for the same contact in less than 30 minutes.
- If a contact is added to a workflow or campaign 50 times within 30 minutes.
In both cases, the system locks the trigger to prevent further strain on the server.
What Should You Do If You Get a Loop Lockout Error?
If you receive a Loop Lockout error, don’t worry. Simply reach out to support for assistance. Our team can review the trigger with you, pinpoint the issue causing the loop, and unlock the trigger once the problem is resolved.
Conclusion
Loop Lockouts are a protective measure against system slowdowns caused by excessive trigger actions. If you encounter this error, contact support to fix the issue and get your system back on track. By understanding and preventing these lockouts, you can ensure your workflows and campaigns run smoothly without wasting server resources.
