Skip to content

Agent workflow: a spec-line run dies at the 45-minute step deadline and ships nothing #3217

Open

Description

@Birfy

Written-by: Chief

What happens

The issue-spec workflow (wf-6c0c757e, nodes read → critique → revise → post) runs each step with the 45-minute default stepTimeoutMinutes. On 2026-11-19 the Cut 20 run run-e64ca077 (task i3114-cut20, started 10:21:12Z) was killed at 11:07:24Z with:

{"code":"step-failed","nodeName":"写规格","text":"step deadline reached (45 min)"}

The whole run then reports failed and nothing is produced: no draft comment, no intake issue, no partial spec. The work spent in that 45 minutes is lost, and the operator only finds out by polling the run list.

The read node legitimately needs that long when it has to verify a candidate against the real tree: in that run it had already downloaded main, applied candidate patches to a scratch copy, and fetched #3112's hunks (runs/i3114-cut20/p3112files.json, p3112_core_src_client_i18n.cjs.patch, red/ tree) when the deadline hit.

Why it matters

Candidate fixes (pick one)

  • A (config): raise stepTimeoutMinutes for this workflow (e.g. 45 → 90). Cheapest, no code.
  • B (behaviour): have the read node post its partial spec as a Draft comment before the deadline, so a timeout still leaves something to continue from.
  • C (watchdog): a run that fails on a step deadline reports the last node + elapsed time to the operator instead of failing silently.

Acceptance

  • A cut that exceeds the read budget either finishes or leaves a Draft comment on the umbrella issue.
  • The run record names the node and the deadline that was hit.

Tier: T3 only if this touches .github/**; the workflow definition itself lives in the app config.

Activity

  1. added
    bugSomething isn't working
    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)
    area:automationScheduled tasks and automation
    on Nov 19, 2026
  2. Birfy commented on Nov 19, 2026

    @Birfy
    CollaboratorAuthor

    A 已落地(45 → 90 分钟);C 早就在;B 改成 brief 层做

    Written-by: Chief / At: 2026-11-19T16:14Z

    A 已做:flybot/workflow/step-timeout 把 wf-6c0c757e(issue-spec)的 stepTimeoutMinutes 从默认 45 提到 90(1..120 内),workflow/state 复核为 stepTimeoutMinutes: 90。改值时该 lane 正跑着 i3114-cut26,已挂的 deadline 按新值 re-arm(#2911 修的正是这条路径)。

    C 不用写:失败记录本来就带节点和时限——run.failure = {code:'step-failed', nodeName:'写规格', text:'step deadline reached (45 min)'},插件还 warn 一次。「操作者只能靠轮询才发现」说的是我的巡检方式,不是引擎缺字段。

    B 不按原样做:从被杀的节点里捞半成品不可靠——它可能正卡在工具调用里,最后一段文本是进度句而不是规格,发成 Draft 反而制造假信号。改成 brief 层纪律:read 节点在跑昂贵验证(拉 main、试补丁、取 #3112 的 hunk)之前,先把候选规格作为 Draft 评论发到 umbrella,再继续验证。这条改的是节点 prompt,等这条 lane 空闲时落地,不占开发线。

    标签:needs-human 去掉——剩下的两条动作(prompt 落地、观察 90 分钟够不够)都归我,不再等 owner。

  3. removed
    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)
    on Nov 19, 2026
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

    area:automationScheduled tasks and automationbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions