deepseek-ai/deepseek-harness · error · HarnessError

SESSION_QUERY_SESSION_NOT_FOUND

SESSION_QUERY_SESSION_NOT_FOUND

Error message

session was not found

What it means

Error "session was not found" thrown in deepseek-ai/deepseek-harness.

Source

Thrown at packages/session-query/tool-session-query/src/service-boundary.ts:79

  },
  SESSION_QUERY_INVALID_SURFACE: {
    code: 'SESSION_QUERY_INVALID_SURFACE',
    message: 'session event history is invalid',
  },
  SESSION_QUERY_INVALID_WINDOW: {
    code: 'SESSION_QUERY_INVALID_WINDOW',
    message: 'session event window is invalid',
  },
  SESSION_QUERY_PERSISTENCE_FAILED: {
    code: 'SESSION_QUERY_PERSISTENCE_FAILED',
    message: 'session history storage is unavailable',
  },
  SESSION_QUERY_SEARCH_DISABLED: {
    code: 'SESSION_QUERY_SEARCH_DISABLED',
    message: 'session search is disabled in this deployment',
  },
  SESSION_QUERY_SESSION_NOT_FOUND: {
    code: 'SESSION_QUERY_SESSION_NOT_FOUND',
    message: 'session was not found',
  },
  SESSION_QUERY_STALE_CURSOR: {
    code: 'SESSION_QUERY_STALE_CURSOR',
    message: 'session history changed while paging; retry the complete search call',
  },
  SESSION_QUERY_SOURCE_CONFLICT: {
    code: 'SESSION_QUERY_TOOL_FAILED',
    message: 'session query operation failed',
  },
} satisfies Record<SessionQueryErrorCode, ModelSafeServiceFailure>

function unauthorizedTarget(): HarnessError {
  return new HarnessError(
    'session target is outside the caller workspace',
    'SESSION_QUERY_TOOL_UNAUTHORIZED',
  )
}

View on GitHub (pinned to b150a551b8)

Solutions

1. Verify the session id and that the session still exists before querying it.

When it happens

Trigger: Thrown at packages/session-query/tool-session-query/src/service-boundary.ts:79 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/61efca3478828f55. Report an issue: GitHub.