deepseek-ai/deepseek-harness · error · HarnessError

SESSION_QUERY_INVALID_CURSOR

SESSION_QUERY_INVALID_CURSOR

Error message

session search continuation is invalid

What it means

Error "session search continuation is invalid" thrown in deepseek-ai/deepseek-harness.

Source

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

  },
  SESSION_QUERY_CORRUPT_SESSION: {
    code: 'SESSION_QUERY_CORRUPT_SESSION',
    message: 'session event history is corrupt',
  },
  SESSION_QUERY_EVENT_NOT_FOUND: {
    code: 'SESSION_QUERY_EVENT_NOT_FOUND',
    message: 'session event was not found',
  },
  SESSION_QUERY_INDEX_FAILED: {
    code: 'SESSION_QUERY_INDEX_FAILED',
    message: 'session search index is unavailable',
  },
  SESSION_QUERY_INVALID_CONFIG: {
    code: 'SESSION_QUERY_TOOL_FAILED',
    message: 'session query operation failed',
  },
  SESSION_QUERY_INVALID_CURSOR: {
    code: 'SESSION_QUERY_INVALID_CURSOR',
    message: 'session search continuation is invalid',
  },
  SESSION_QUERY_INVALID_FILTER: {
    code: 'SESSION_QUERY_INVALID_FILTER',
    message: 'session query filters were rejected',
  },
  SESSION_QUERY_INVALID_LIMIT: {
    code: 'SESSION_QUERY_INVALID_LIMIT',
    message: 'session query result limit was rejected',
  },
  SESSION_QUERY_INVALID_QUERY: {
    code: 'SESSION_QUERY_INVALID_QUERY',
    message: 'session query was rejected',
  },
  SESSION_QUERY_INVALID_LINEAGE: {
    code: 'SESSION_QUERY_INVALID_LINEAGE',
    message: 'session lineage is invalid',
  },

View on GitHub (pinned to b150a551b8)

Solutions

1. Discard the stale continuation token and restart the search from the first page.

When it happens

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