MC-4256 — [watchdog:dispatch:ticket-pickup:MC-4253] Dispatch anomaly hidden in completed run: ticket-pickup

Home Board MC-4256

[watchdog:dispatch:ticket-pickup:MC-4253] Dispatch anomaly hidden in completed run: ticket-pickup

Core scheduler task `ticket-pickup` completed at 2026-05-26 15:50:03, but its captured output contains a dispatch/revert error. The task row is marked completed, so normal faile...

State Done Next Action Closed Owner Luci Runtime Closed Age 18d ago

Description

MC-4256

Core scheduler task `ticket-pickup` completed at 2026-05-26 15:50:03, but its captured output contains a dispatch/revert error. The task row is marked completed, so normal failed-run monitoring would miss it. Ticket/run key: `MC-4253` No newer clean run of the same core task and no active runtime for the affected ticket was found, so this needs Luci triage. Captured output excerpt: ``` Orchestrator inbox drain: 8 item(s) routed Found 1 MC worker todo ticket(s), 1 workers active, 1 slot(s) free ERROR dispatching MC-4253 to ticket runtime: HTTP Error 409: CONFLICT Reverted MC-4253 -> todo (tmux spawn failed) No larry tickets to pick up. ```

Activity

done

Luci is working...

Details — Done · High · Luci ▼

State

Done

Closed

State

Priority

People

Owner (assigned to)

Controller

Timing / Details

Due Date

Snooze

Source scheduler-watchdog (scheduled)

Project infra

Created 18d ago

Updated 18d ago

Advanced / Operator evidence

Routing owner

Routes via

Operator console

Evidence

Ticket is done; runtime is closed. ticket_marked_done profile claude_opus_1m_medium · cwd /home/lucienne/workspace · uptime 17d 18h · last activity 17d 16h ago MC is visibility-only. Hermes Luci launches and gates work outside MC, then mirrors evidence/status here. Raw console: luci · claude/anthropic/opus[1m]

Workflow

Start Dev Review + QA ▾

Select phases to include:

Research (scott) Implement (larry) (required) Council Review (council) Code Review (luci) Validate (tessa) (required) Sign-off (atlas)

Agents

Review Gates

Decision

WAT routing: choose an agent, review gate, or decision. Buttons use the live runtime when one is attached.

Luci 18d ago

QUESTION: when you need MC to reflect the next state. [2026-05-26 13:48] luci: Ticket runtime send failed while dispatching. root_cause: HTTP Error 409: CONFLICT ● plugin:context-mode:context-mode - ctx_execute (MCP)(language: "shell", code: "cd ~/workspace\necho \"=== tmux sessions matching MC-4253 ===\"\ntmux ls 2>/dev/null | grep -i 4253 || echo \"no tmux\"\necho\necho \"=== MC-4253 current status ===\"\nsqlite3 mission-control/mc.db \"SELECT id, status, assigned_to, updated_at FROM tickets WHERE id='MC-4253';\"\necho\necho \"=== runtime sessions for MC-4253 ===\"\nsqlite3 mission-control/mc.db \"SELECT session_id, status, created_at, last_activity FROM runtime_sessions WHERE ticket_id='MC-4253' ORDER BY created_at DESC LIMIT 5;\" 2>/dev/null\necho\necho \"=== mc_pickup current attempts ===\"\nsqlite3 mission-control/mc.db \"SELECT name, value FROM kv WHERE name LIKE '%4253%';\" 2>/dev/null\necho\necho \"=== recent dispatch attempts log ===\"\nls -lt logs/mc_pickup*.log 2>/dev/null | head -3\n") ⎿ ⚠️ context-mode v1.0.111 outdated → v1.0.151 available. Upgrade: /ctx-upgrade === tmux sessions matching MC-4253 === no tmux === MC-4253 current status === === runtime sessions for MC-4253 === === mc_pickup current attempts === === recent dispatch attempts log === -rw-r--r-- 1 lucienne lucienne 3524306 May 26 16:05 logs/mc_pickup.log

luci 18d ago

Luci picking up this ticket (background worker).

luci 18d ago

Ticket picked up by Luci via MC dispatcher. MC-4256: [watchdog:dispatch:ticket-pickup:MC-4253] Dispatch anomaly hidden in completed run: ticket-pickup Work this ticket in the live tmux runtime. Use DONE:, REVIEW:, or QUESTION: when you need MC to reflect the next state.

api 18d ago

Closed (orchestrator). System working as designed. MC-4253 is now in 'todo' (updated 16:01) — dispatcher's 409 was caught and force-safe-reverted to todo per MC-4236 hardening. Next pickup cycle will retry. Watchdog correctly flagged the hidden 409 inside the 'completed' run, but no orphan state was left. No fix needed.