Workflows can sometimes trigger each other—or themselves—in a repeated cycle. This is called an infinite loop, and it can rapidly consume your monthly workflow step-run credits.
This guide explains what causes loops and how to prevent them.
What Is an Infinite Loop?
An infinite loop happens when:
- A workflow triggers itself over and over, or
- One workflow triggers another, which then triggers the first again
This cycle keeps running until your step-run credits run out.
Example:
- Trigger: “When a contact is updated”
- Action: “Update the same contact”
- This action reactivates the trigger, causing the workflow to run endlessly.
How Loops Can Happen
Infinite loops usually occur when:
1. A Trigger Watches the Same Data That an Action Changes
- For example:
- Trigger: “Contact Updated”
- Action: “Update Contact → Field X”
- This update makes the trigger fire again.
2. Workflow A Activates Workflow B, Which Activates Workflow A
- Two workflows unintentionally call each other repeatedly.
3. Multiple Actions Modify a Field That Another Workflow Is Monitoring
- A change made in one workflow triggers another workflow watching that same field.
Why Infinite Loops Are Dangerous
If a loop starts:
- It runs non-stop
- It consumes your step-run credits extremely fast
- Other workflows may stop running due to credit depletion
- The loop only ends when credits are exhausted or the workflow is manually deactivated
How to Prevent Infinite Loops
Here are the best practices to avoid loops when building workflows:
1. Avoid Using “Update” Actions on Fields Your Trigger Is Watching
- If your trigger is “Contact Updated,” avoid updating fields that will retrigger it.
- Add Conditions or Filters
- Use conditional steps so actions only run when necessary.
- Do Not Chain Workflows Unnecessarily
- Only trigger another workflow if absolutely needed. Avoid mutual triggers between two workflows.
- Test Carefully Before Activating
- Run small tests and verify that the workflow does not re-trigger itself.
- Review Your Steps When Using Auto-Update Actions
- Examples:
- Update Contact
- Update Deal
- Update Task
- These actions can easily create accidental loops.
What We Do to Protect You
To help prevent unwanted loops:
- A confirmation warning appears before activating any workflow
- Step-run usage shows in real time, so you can stop a loop quickly
Still, the safest approach is to double-check your logic before activating.
Need Help?
If you’re unsure whether your workflow might cause a loop, contact our support team—we’re happy to review your workflow logic and help you avoid issues.