deepseek-ai/deepseek-harness · error · HarnessError

SESSION_QUERY_INVALID_SURFACE

SESSION_QUERY_INVALID_SURFACE

Error message

session event history is invalid

What it means

Error "session event history is invalid" thrown in deepseek-ai/deepseek-harness.

Source

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

  },
  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',
  },
  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',
  },

View on GitHub (pinned to b150a551b8)

Solutions

1. Fix the history request arguments (valid session id, valid range) and retry.

When it happens

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