deepseek-ai/deepseek-harness · error
schedule: dispatch append failed for agent "${this.agent.id}
Error message
schedule: dispatch append failed for agent "${this.agent.id}": ${renderThrown(error)} What it means
Error "schedule: dispatch append failed for agent "${this.agent.id}": ${renderThrown(error)}" thrown in deepseek-ai/deepseek-harness.
Source
Thrown at packages/schedule/schedule/src/runtime.ts:302
this.agent.session.append('schedule/change', {
version: 1,
operation: 'dispatch',
id: decision.record.id,
})
} else {
for (const reminder of decision.reminders) {
this.agent.session.append('schedule/change', {
version: 1,
operation: 'dispatch',
id: reminder.record.id,
acceptedAt: decision.acceptedAt,
})
}
}
} catch (error: unknown) {
this.faulted = true
this.clearTimer()
this.ctx.logger.warn(`schedule: dispatch append failed for agent "${this.agent.id}": ${renderThrown(error)}`)
return Promise.resolve(false)
}
return Promise.resolve(true)
})
} catch (_busy: unknown) {
// `runMaintenance` rejects synchronously only while another agent activity owns the idle phase.
if (this.isLive()) this.waitForIdle()
return
}
if (!await maintenance) return
try {
await flushSchedulePersistence(this.ctx, this.agent.session)
} catch (error: unknown) {
if (this.isLive()) {
this.ctx.logger.warn(`schedule: dispatch barrier failed for agent "${this.agent.id}": ${renderThrown(error)}`)
}
returnView on GitHub (pinned to b150a551b8)
Solutions
- Inspect the embedded error from the dispatch append and fix the persistence or session-write failure it names.
When it happens
Trigger: Thrown at packages/schedule/schedule/src/runtime.ts:302 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of deepseek-ai/deepseek-harness@b150a551b8 (2026-08-24).
Data as JSON: /api/errors/e36ad3f85d1ea641.
Report an issue: GitHub.