deepseek-ai/deepseek-harness · error

telemetry: backend shutdown failed: ${String(error)}

Error message

telemetry: backend shutdown failed: ${String(error)}

What it means

Error "telemetry: backend shutdown failed: ${String(error)}" thrown in deepseek-ai/deepseek-harness.

Source

Thrown at packages/session/session-telemetry/src/coordinator.ts:123

          this.relayAgentError(agent, turn, step, error)
        })
      })
      for (const session of ctx.sessions.list()) {
        this.adopt(session)
      }
    }
    ctx.effect(() => async () => {
      // Sessions still adopted here are alive through whole-application
      // teardown, so capture the marker before the backend quiesces.
      for (const session of this.adopted) {
        this.contain(() => {
          this.deliver(session, { record: this.redact(shutdownRecord(session)) })
        })
      }
      try {
        await this.backend.shutdown()
      } catch (error) {
        this.ctx.logger.warn(`telemetry: backend shutdown failed: ${String(error)}`)
      }
    }, 'telemetry capture')
  }

  /**
   * Project and hand over the canonical session-log suffix after the handoff
   * cursor, optionally stopping at an inclusive sequence boundary. Redaction
   * runs during this call, so an on-demand caller retains no copied records
   * before requesting capture and uses the policy mounted at that time.
   * Backend and policy failures remain contained per event and do not starve
   * later events in the same replay.
   * @param session - session whose current canonical-log prefix may be handed over.
   * @param throughSeq - optional last sequence included in this capture.
   */
  captureSession(session: Session, throughSeq?: number): void {
    const cursor = handoffCursor.get(session) ?? session.firstLiveSeq - 1
    // Containment is PER EVENT: one rejected record is withheld fail-closed
    // while the rest of the historical replay proceeds.

View on GitHub (pinned to b150a551b8)

Solutions

1. Inspect the telemetry backend shutdown error and fix the backend's close/flush path.

When it happens

Trigger: Thrown at packages/session/session-telemetry/src/coordinator.ts:123 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/63f70bc2dd522df7. Report an issue: GitHub.