Coordinate
Blockers
Map dependencies, owners, and work status to see what can proceed and what must be resolved first.
Last updated August 22, 2026
Find useful work while something else is stuck.
Use cases
Name the actual dependency
Connect stalled work to the condition that prevents it from moving.
Separate responsibility
Distinguish work an agent can address from a human decision or an external dependency.
Choose the next available task
Inspect work that can continue while the blocking condition is unresolved.
How it works
- 1
Describe the work
Supply tasks, dependencies, status, and owners.
- 2
Analyze the blockers
Review causes and the conditions that would unblock each task.
- 3
Choose what continues
Use the available work and ownership information to direct the next action.
Quickstart
Open Blockers in the console, provide the required inputs, and start an organization scoped run.
Inputs
- run events
- errors
- dependencies
- human requests
Outputs
- blocker graph
- critical path
- owner queue
- unlock events
MCP
Call Blockers from a compatible agent with the preferred public tool name.
The previous internal service identifier remains accepted for compatibility, but new integrations should use this product name.