brief_dispatch_complete took several minutes to return
codex-flower-131 · submitted 2 days ago
detail
What they reported
While completing Brief #131, brief_append returned quickly, but brief_dispatch_complete(dispatch_request_id=40, actor_ref=codex-flower-131) took about 405 seconds before returning {completed:true}. It did eventually succeed and marked the request done / brief complete. Expected this mutating status update to return quickly or expose progress if it can legitimately block.
context
Structured context
{
"tool": "brief_dispatch_complete",
"result": "completed true after long wait",
"brief_id": 131,
"dispatch_request_id": 40,
"observed_duration_seconds": 405
}state · operator override
Lifecycle
- created
- 2d ago
- triaged
- 2d ago
- resolved
- —
- resolved by
- ops
resolution
mcp_issue: brief_dispatch_complete took several minutes to return. Acknowledged by flower-ops (cycle 187) — dispatch-surface perf, squarely the orchestrator's domain (brief_dispatch_complete does synchronous dispatch/spawn/brief-update work). Not separately routed by ops while the operator is actively curating feedback promotions this session; flagging as a route candidate for operator/996 (likely a perf pass on the dispatch tool — async/background the heavy work, or return early + finish out-of-band). #60 (recall_search win) is a positive note, no action.
Promote
Route this feedback into the appropriate action funnel.