Hmbown/CodeWhale · error
Fleet coordination state is busy; retry resume
Error message
Fleet coordination state is busy; retry resume
What it means
Error "Fleet coordination state is busy; retry resume" thrown in Hmbown/CodeWhale.
Source
Thrown at crates/tui/src/fleet/manager.rs:681
// Reuse the shared scheduler recovery engine over the same ledger so
// resume and steady-state supervision converge on one store and one
// retry/escalation policy. The manager's `stale_after` becomes the
// scheduler's heartbeat timeout so both surfaces agree on staleness.
let policy = FleetSchedulerPolicy {
heartbeat_timeout: self.stale_after,
..FleetSchedulerPolicy::default()
};
let mut scheduler = FleetScheduler::open(&self.workspace, policy)?;
scheduler.set_now(now);
// Keep the lock order coordination -> ledger. A restart generation is
// durably prepared by the callback before the scheduler publishes the
// replacement lease, and an exact one-generation-ahead preparation is
// safe to consume after a process crash.
let mut coordination_guard = match &self.sub_agent_manager {
Some(manager) => Some(
manager
.try_write()
.map_err(|_| anyhow!("Fleet coordination state is busy; retry resume"))?,
),
None => None,
};
let report = scheduler.resume_run_with_restart_callback(
run_id,
|state, task, task_spec, worker_id| {
if let Some(guard) = coordination_guard.as_mut() {
self.prepare_registered_restart_generation(
guard, state, task, task_spec, worker_id,
)?;
}
Ok(())
},
)?;
let status = self.run_status(run_id)?;
Ok(FleetResumeReport {
run_id: run_id.clone(),
reclaimed_stale: report.marked_stale,View on GitHub (pinned to 8880682c63)
When it happens
Trigger: Thrown at crates/tui/src/fleet/manager.rs:681 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of Hmbown/CodeWhale@8880682c63 (2026-08-16).
Data as JSON: /api/errors/119b19f92760d5d9.
Report an issue: GitHub.