deepseek-ai/deepseek-harness · error · SchedulePersistenceError

Schedule persistence did not complete.

Error message

Schedule persistence did not complete.

What it means

Error "Schedule persistence did not complete." thrown in deepseek-ai/deepseek-harness.

Source

Thrown at packages/schedule/schedule/src/persistence.ts:26

  /**
   * Construct a contained persistence failure.
   * @param cause - Rejection returned by the shared barrier, when present.
   */
  constructor(cause?: unknown) {
    super('Schedule persistence did not complete.', cause === undefined ? undefined : { cause })
    this.name = 'SchedulePersistenceError'
  }
}

/**
 * Require one successful shared persistence checkpoint.
 * @param ctx - Context carrying the live session store.
 * @param session - Exact live session to checkpoint.
 * @returns After at least one listener explicitly acknowledges completed durability work.
 */
export async function flushSchedulePersistence(ctx: Context, session: Session): Promise<void> {
  try {
    if (!await ctx.sessions.flush(session)) throw new SchedulePersistenceError()
  } catch (error: unknown) {
    if (error instanceof SchedulePersistenceError) throw error
    throw new SchedulePersistenceError(error)
  }
}

View on GitHub (pinned to b150a551b8)

Solutions

1. Retry the persistence operation and check the underlying store error; do not treat the schedule as saved.

When it happens

Trigger: Thrown at packages/schedule/schedule/src/persistence.ts:26 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/42c5812322beb212. Report an issue: GitHub.