deepseek-ai/deepseek-harness · error · AggregateError
workspace '${id}' record deletion and registry-order rollbac
Error message
workspace '${id}' record deletion and registry-order rollback both failed What it means
Error "workspace '${id}' record deletion and registry-order rollback both failed" thrown in deepseek-ai/deepseek-harness.
Source
Thrown at packages/workspace/workspace/src/index.ts:383
archivedSessionIds: state.archivedSessionIds,
}
await this.setState({
...nextState,
pendingMutation: { operation: 'delete', workspaceId: id },
})
this.entities.delete(id)
try {
await this.requireTable().delete(id)
} catch (error) {
this.entities.set(id, entity)
try {
await this.setState(state)
} catch (rollbackError) {
// The durable marker still says to finish deletion, so the cache must
// agree with that recoverable direction rather than republish a row
// absent from the persisted order.
this.entities.delete(id)
throw new AggregateError(
[error, rollbackError],
`workspace '${id}' record deletion and registry-order rollback both failed`,
)
}
throw error
}
try {
await this.setState(nextState)
} catch (error) {
// The deletion committed at the table write and was already published
// to Host streams. Keep the durable marker for startup recovery rather
// than reporting failure after the requested state became true.
this.ctx.logger.warn(
`workspace '${id}' was deleted but its pending marker could not be cleared: ${String(error)}`,
)
}
return true
}View on GitHub (pinned to b150a551b8)
Solutions
- Restore writability of the workspace store, then reconcile the leftover record or registry-order entry manually.
When it happens
Trigger: Thrown at packages/workspace/workspace/src/index.ts:383 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/108a8dfc18b41f47.
Report an issue: GitHub.