Skip to main content

Understanding Loop Lockouts in Stack

Loops can occur when two triggers interact in a way that causes them to repeatedly activate each other, or when a single trigger continuously activates itself. This creates an infinite loop of actions that can negatively impact the performance of Stack by overloading server resources. To prevent this, Stack actively monitors for potential loops and automatically locks any triggers that might cause them.

What Causes a Loop Lockout?​

A loop lockout happens when workflows, triggers, or campaigns execute 50 times for the same contact within a 30-minute window. Here are some examples to illustrate this:

  • A trigger activates 50 times for the same contact in under 30 minutes.
  • A contact is added to a workflow or campaign 50 times within the same timeframe.

Resolving Loop Errors​

If you encounter a loop error, don't worry! Our support team is here to help. Simply reach out to Stack Support, and we'll work with you to review the trigger, identify what's causing the loop, and unlock the trigger so you can continue using your workflows smoothly.

Feel free to contact us with any questions or concerns about loop lockouts. We're here to ensure your experience with Stack is seamless and efficient.