Use when
- A workflow phase should release after enough unique agents arrive.
- The synchronization point can safely expire after a bounded interval.
coordination · beta · free
Atomically records opaque participant arrivals against a fixed threshold and TTL. Repeated arrivals by the same participant are idempotent, and the barrier stays released until it expires.
{
"input": {
"action": "arrive",
"namespace": "pipeline:example.invalid",
"key": "phase-rendered",
"participant": "agent-a",
"threshold": 3,
"ttl_seconds": 60
},
"output": {
"action": "arrive",
"barrier_hash": "sha256:bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
"exists": true,
"configuration_matches": true,
"newly_arrived": true,
"threshold": 3,
"participant_count": 1,
"released": false,
"expires_at": "2026-07-24T12:01:00.000Z"
},
"negative": [
{
"scenario": "Every named participant must arrive or participant identities must be listed.",
"expected_error": "INVALID_INPUT",
"charged": false
}
]
}| Code | Retry | Charged | Recovery |
|---|---|---|---|
| INVALID_INPUT | false | false | Correct the request to match input_schema. |
| TOOL_PAUSED | true | false | Wait for the operator to resume the tool. |
| RATE_LIMITED | true | false | Retry after the response Retry-After interval. |
| DEPENDENCY_UNAVAILABLE | true | false | Retry with the same idempotency identity. |
The HTTP, OpenAPI, MCP, llms.txt, and ARD descriptions are generated from this same registry record.