Who This Is For / When to Use
This article is for Kyrios users who see a message that a Workflow, Trigger, or Campaign has been locked due to a loop and need to understand why it happened and how to resolve it.
What a Loop Is in Workflows, Triggers, or Campaigns
A loop occurs when automations repeatedly trigger each other or trigger themselves, causing the same contact to enter the same automation over and over in a short period of time.
Common loop scenarios include:
Two triggers that add a contact to each other’s workflows.
A workflow action that re-triggers its own starting condition.
Multiple workflows acting on the same contact without filters or exit conditions.
Loops create infinite execution cycles unless stopped.
Why Loop Lockouts Exist
Loop lockouts exist to protect system performance by stopping automations that consume excessive server resources.
When loops run unchecked, they can:
Flood the system with repeated executions.
Slow down automation processing for all users.
Create unexpected contact behavior and data changes.
To prevent this, Kyrios actively monitors automation activity and applies a lock before performance is impacted.
When a Workflow, Trigger, or Campaign Gets Loop Locked
Kyrios applies a Loop Lock when the same contact starts or executes the same automation 50 times within 30 minutes.
This includes:
A trigger firing 50 times for one contact in less than 30 minutes.
A contact being added to the same workflow or campaign 50 times in less than 30 minutes.
Once this threshold is reached, the automation is automatically locked and placed into Draft status.
What “Loop Locked” Means
When an automation is Loop Locked, Kyrios temporarily disables it to stop further executions.
While locked:
The Workflow, Trigger, or Campaign cannot be activated.
New contacts will not enter the automation.
Existing executions are halted.
The automation remains locked until Support reviews and unlocks it.
What to Do If You Receive a Loop Lock Error
If a Loop Lock message appears, Support intervention is required before the automation can be reactivated.
Steps to take:
Do not attempt to duplicate or re-enable the automation.
Review the trigger and workflow logic for actions that may re-add the same contact.
Contact Kyrios Support and request a loop review.
Work with Support to correct the automation logic.
Have Support unlock the Workflow, Trigger, or Campaign once the loop risk is resolved.
How to Identify What Caused the Loop
The source of a loop can usually be identified by reviewing execution history.
To investigate:
Open the Workflow History or Execution Logs.
Look for a single contact appearing dozens of times in a very short time window.
Trace the action or data change that caused the contact to re-enter the automation.
This information helps pinpoint exactly which step or trigger caused the loop.
How to Prevent Loop Lockouts
Loops can be avoided by adding safeguards to automation logic.
Best practices include:
Adding filters to prevent re-entry for the same contact.
Using exit conditions or goal steps.
Avoiding circular triggers between workflows.
Ensuring one automation does not modify data that retriggers itself.
Preventive design reduces the risk of future loop lockouts.
Frequently Asked Questions
What is a loop in Workflows, Triggers, or Campaigns?
A loop happens when automations repeatedly trigger each other or trigger themselves, creating an endless cycle of executions for the same contact.
Why are loops a problem?
Loops consume excessive server resources and can slow down automation processing for all users, which is why the system automatically stops them.
When does Kyrios apply a Loop Lock?
A Loop Lock is applied when the same contact triggers or is added to the same automation 50 times within 30 minutes.
What does it mean when an automation is Loop Locked?
It means the automation has been temporarily disabled to prevent performance issues and must be reviewed before being reactivated.
Can I unlock a Loop Locked automation myself?
No. Loop Locked automations must be reviewed and unlocked by Kyrios Support after the loop condition is resolved.
How can I see which contact caused the loop?
Check the Workflow History or Execution Logs and look for one contact repeatedly appearing in a short time span.