QueryExecutionFailure_TelemetryData: QueryBuilderTelemetryContext & TelemetryErrorFields & {
    executionDurationMs?: number;
    executionTraceId?: string;
    queryInfo?: QueryBuilderQueryInfo;
    timings?: TimingsRecord;
} & Record<string, unknown>

Payload for query execution / plan / export failure events. Mirrors the shape of LegendQueryTelemetryHelper creator-failure payloads (errorName, errorMessage, httpStatus) so success/failure pairs can be joined on the same set of dimensions.

Type declaration

  • OptionalexecutionDurationMs?: number
  • OptionalexecutionTraceId?: string

    Backend trace ID for the failed execution, when the error carries one.

  • OptionalqueryInfo?: QueryBuilderQueryInfo
  • Optionaltimings?: TimingsRecord

    Phase timings collected up to the point of failure. Which laps are missing is the useful signal: no graph-manager.v1.engine-operation.server-call.success means the query never reached the engine, so the failure is pre-flight rather than in-flight.