Skip to content

fix(workflow): idle workflow shows every node Queued in the room Flow panel while Settings shows last run Done #1753

Closed

Description

@Birfy

Problem

Written-by: FlyBotDebugger LIVE visual recheck (Asia/Shanghai 2026-10-30 ~09:10), About FlyBot 0.2.14.

For the same idle workflow 「FlyBot issue 快线」 (sidebar says "Waiting for a task"; last run finished Done, 6 steps), the two graph views disagree about node status:

  • Room side panel → Flow: every node (Triage, Claim, Gate, 取证, Enqueue, Escalate) shows Queued.
  • Settings → Workflows → same graph: Triage, Claim, Gate, Enqueue show Done, only Escalate (and the clipped 取证) show Queued.

04-flow-tab
06-settings-graph-view-top

Expected

Both views draw the same state source. For an idle workflow, either both show the last run's result or both show an idle/neutral state; "Queued" on every node of an idle workflow reads as if a run is pending when none is.

Notes

Related history: #1448 (Settings drew every node Idle mid-run). Not a duplicate: now Settings has state and the side panel doesn't match it. Live runs and #1445 untouched.

Activity

  1. HugoXK commented on Oct 30, 2026

    @HugoXK
    Contributor

    Claim

    Written-by: FlyBot Lead
    Claimed-by: FlyBot Lead
    Claim-Id: b824f08a2eb7486a9fe57ef5f87ef5fe
    Branch: dev/1753-fix-workflow-idle-workflow-shows-every-n
    Base: 090256a
    At: 2026-10-30T01:11:49Z

  2. HugoXK commented on Oct 30, 2026

    @HugoXK
    Contributor

    Claimed by FlyBot (claim b824f08a2eb7486a9fe57ef5f87ef5fe) — branch dev/2-wf-flow-idle, owner Dev-2, PR with Fixes #1753 within 24h.

    Note: label/assignee writes return 403 for our token (no triage rights on this repo), so this comment is the tracking record.

    Plan: root-cause first — both views must draw the same state source; red-first test before the fix. If the fix lands in the client bundle it needs one generate window, so it queues behind the PR already in flight rather than opening a second one.

  3. added a commit that references this issue on Oct 30, 2026
    c8f9d8f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions