Workflow Waits on Step That Waits Back

What This Looks Like

A workflow step cannot continue until another step completes, but that other step also depends on the first one. The AI, reviewer, tool, approval path, or routing step may keep waiting for a condition that cannot be satisfied because the dependency points back to itself through another part of the workflow.

Why It Matters

Circular waiting creates stalled work. Users may see the workflow sit in pending, review, blocked, or waiting states without a clear failure message. Because each step appears to be waiting correctly, the real problem can be hidden in the dependency structure.

Structural Signal

Two or more workflow steps depend on each other in a way that prevents resolution. The issue is not simply that a step is slow or missing; it is that the dependency path creates a loop with no valid next step.

Common Triggers

• A review step waits for an output that depends on review completion
• A tool call waits for approval that depends on the tool result
• Handoff conditions are declared separately and point back to each other
• Workflow state is split across systems without a shared dependency map
• Escalation requires a status that cannot be produced until escalation completes
• The process lacks a base case or override for circular waits

When to Use This Issue

Use this Issue when a workflow is blocked because one step waits on another step that ultimately waits back on the first step.

When Not to Use This Issue

Do not use this Issue for ordinary delays, unavailable reviewers, or missing inputs unless the missing input is caused by a circular dependency in the workflow.