> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/troubleshooting/loop-lockouts-in-workflows.md). # Loop Lockouts in Workflows Loops occur when two Triggers either feed into each other or one Trigger feeds back into itself, creating an infinite loop of actions. Loops are detrimental to app performance because they commandeer server resources, causing a slowdown for all users, which is why the system now looks for potential loops and locks the Triggers that may cause them. Workflows, Triggers, and Campaigns will be Loop Locked when they hit 50 Starts/Executions for the same Contact in less than 30 minutes. Example: Trigger fires 50 times for the same Contact in less than 30 minutes, or a Contact gets added to a Workflow/Campaign 50 times in less than 30 minutes. If you receive a Loop error, please contact Support so that we can review the Trigger with you, fix what would cause a loop, and unlock the Trigger. This can also occur when there are multiple workflows without a filter involved. {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://software-help-docs.gitbook.io/knowledge-base/software-guide/troubleshooting/loop-lockouts-in-workflows.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.