Summary
We have added two clear indicators when a potential circular reference is present in workflow configuration. A workflow that calls itself (or forms a loop with other workflows) can cause issues at runtime if it is not designed to handle the circular reference.
PLEASE NOTE: The option to run the current workflow remains available; we are not blocking this behavior. There is no breaking change; existing workflows that use this pattern continue to work.
Where this applies
In the Admin Workflow configuration
- Tooltip in the Workflow to Run dropdown. On the workflow config screen, in the “Workflow to Run” dropdown, we display a tooltip that says “Potential circular reference” when you select a workflow that would create a potential circular reference.
Warning banner on Save. When you save a workflow that has a potential circular reference (e.g., a Run Workflow action that targets the current workflow), a warning banner is displayed. It says: “Potential circular reference configured between parent and child workflows. Disregard if this is intentional.”
Why we are making this change
- Reduce accidental misconfiguration when a workflow is not designed to handle a circular reference.
- Support intentional use by surfacing the warning banner and tooltip so you can confirm a circular reference is deliberate before or when saving.
- Ensure anyone configuring or saving a workflow sees clearly when a potential circular reference is present and can avoid runtime issues.
What you need to do
- No action is required; this is a guidance and awareness change only.
- When you see the tooltip “Potential circular reference” in the Workflow to Run dropdown or the warning banner on Save, treat it as a reminder to confirm the circular reference is intentional and that your workflow is designed to handle it.
When we are enabling this change
Sandbox tenants: March 19, 2026
Production tenants: April 2, 2026