Repository navigation
fix(workflow): idle PR Workflow still shows a Queued strip for a failed past run #1469
Description
Problem
LIVE prod 「FlyBot PR → 合入」 with no live run (activeCount 0; history only failed #1422 / #1395):
- Sidebar preview: 「Waiting for a task」
- Stage still shows a task strip for fix(palette): read a stored line's words in a ⌘K row, not its fence markers or trace #1395 with badge Queued (and Progress / Flow), not Failed / Idle
- Details / Runs correctly show past failures, so the stage header disagrees with reality
Related-but-different from #1424 (reaped run keeps nodeStatus running / "Running now"). Here the lane is idle and history is failed, yet the strip still presents a queued/waiting past task.
Expected
When activeCount is 0 and the last runs failed (or there is no live run), the stage strip should read Failed / Idle (last run failed) — not Queued on a stale task card — and match 运行记录.
Context
- Prod tip
952d6358 - Do not merge to prod without owner yes.
Owner
Birfy / bot-im / FlyBotDebugger visual pass 1
Activity
Birfy commentedon Oct 27, 2026
Screenshots (LIVE prod tip 952d635, 2026-10-27 Asia/Shanghai)
Birfy commentedon Oct 27, 2026
Screenshots (LIVE prod tip
952d6358, 2026-10-27 Asia/Shanghai)Polish workflow UI: compact assign rows, fix status badges, improve t…
Polish workflow UI: compact assign rows, fix status badges, improve t…
Birfy commentedon Oct 27, 2026
Pass 5 residual (LIVE prod, unupgraded — still #1465+#1467+#1473 pending)
Written-by: FlyBotDebugger visual pass 5
#1469 is CLOSED (fixed in #1473), but LIVE prod still shows the contradictory Queued vs Failed chrome on 「FlyBot PR → 合入」 with no live run:
开始 · #1395(and prior assign/start lines) — no failed line for the red strip / Failed runsNot opening a new Queued-vs-Failed issue; this is residual evidence on prod until the upgrade that includes #1473. Leave #1445 untouched; no prod-upgrade ask from this pass.