t3_queue_reorder can't move a message ahead of queued automatic completion deliveries#25644
What happened
t3_queue_reorder won't move a queued message ahead of any queued automatic completion delivery:
| 1 | t3_queue_reorder({ threadId: "mcp:launch:870f4a9a-16a6-4ff8-a844-a7c824708e01:issue-dispatcher-v1", |
| 2 | queuedRunId: "…issue-dispatcher-v1:ordinal:4329", beforeRunId: "…issue-dispatcher-v1:ordinal:4223" }) |
| 3 | → orchestration_error: "Queued messages cannot be reordered ahead of automatic completion delivery." |
(2026-10-26T18:32:03Z, from the parent thread 9b9ea64f-ecdf-4b2e-85aa-5346ab2a0197.) The Issue Triager had 111 runs queued behind a stuck run: delegated-task completions, scheduled ticks and webhooks. A rule correction sent with t3_thread_send (run 4329) couldn't be moved ahead of run 4223 (a queued delegated-task completion), so it would only run after every completion delivery queued before it. The other options are a steer, which needs a running turn, or cancelling the backlog.
Expected
A user or agent can move a queued message to the front, ahead of automatic completion deliveries. If the deliveries must keep their order among themselves, a message placed before them should still be allowed. If this stays refused, the error should say how to get a message in first.
Where
apps/server/src/orchestration-v2/Orchestrator.ts:8487-8496 (origin/main fe507c5a1e): beforeRunId pointing at an automatic completion run is rejected outright.