Skip to content

orchestration: restored Codex terminal reuse times out before task injection (recurrence of #1) #45

Open

Description

@DoozyX

Observed recurrence of the timeout symptom in closed issue #1; shared root cause is UNKNOWN. Related open #29 reports terminal_handle_stale, a different observed error; this entry reports restored-terminal reuse returning timeout.

orca --version retained output: 1.4.238-local.1792814572196.b76579683cfd.

Expected: a retained Codex terminal accepts its next Task, or reports a precise unusable-session identity/recovery disposition. Actual: three retained starts failed at agent_readiness with lastError=timeout, no accepted task brief and empty residualResources. Fresh Codex replacements accepted input on the same Tasks without resetting budgets.

Exact diagnostic command preserved in the accepted retrospective:

orca orchestration worker-show --dispatch ctx_d48ae9f7d386 --json

It reports failed readiness, dispatched 2026-10-24 09:27:13, completed 2026-10-24T09:28:13.056Z, startOptions.timeoutMs=60000, and later observation status=identity_changed, exactWorker=false. The later observation does not establish the cause of the earlier timeout.

Literal original launch argv: UNKNOWN (not preserved). Root cause: UNKNOWN. This is observed evidence, not an invented executable reproduction. Durable start options for the diagnostic Dispatch retain the existing terminal, existing worktree, terminal/user_default mode, timeout 60000, setup not_applicable/existing_worktree, and null agent/model/effort selections. Sanitized excerpts below redact only private placement:

{"worktree":"path:<REDACTED-private-worktree>","terminal":"term_2f2cb540-f79f-4e77-8f8d-50db2ff14f96","agent":null,"timeoutMs":60000,"setup":"not_applicable","setupSource":"existing_worktree"}

Three retained failure → fresh accepted-input receipt pairs, each pair on the same Task:

Pair Failed Dispatch Fresh Dispatch Receipt names under local run tmp/
A ctx_d48ae9f7d386 ctx_57fceb6aefc2 518-fix1-launch.json / 518-fix1-retry-launch.json
B ctx_a39c6e3efa4e ctx_49212534106d 519-recovery4-launch.json / 519-recovery4-retry-launch.json
C ctx_129c0086f41d ctx_2cdbe97de069 520-e2e-pr1-launch.json / 520-e2e-pr1-retry-launch.json

Each failure has state=failed, stage=agent_readiness, failedStage=agent_readiness, lastError=timeout, terminal action reused and residualResources=[]. Each fresh receipt has terminal action created, state=ready, stage=input_accepted, turnStart=observed, effective Codex/gpt-6.1-sol/medium and timeout60000. Successful replacement is not a root-cause fix claim, and missing contact was not treated as process death.

Accepted local retrospective: .orca/2026-10-23-todo-issues/orchestrate/retrospective.md, Orca issues / “Restored Codex terminal reuse times out before task injection (repeat; cause unproven)”. Earlier evidence: .orca/2026-10-05-open-issues-482-486/orchestrate/retrospective.md. Retained diagnostic/version receipts: tmp/retrospective/readiness-show.json and version.json. Private checkout paths are redacted; no raw private files are attached.

Activity

  1. added
    retroFiled by a delivery retrospective; auto-fixed by the retro automation
    on Oct 24, 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

    retroFiled by a delivery retrospective; auto-fixed by the retro automation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions