linear-common-errors

# Linear Common Errors ## Overview Quick reference for diagnosing and resolving common Linear API and SDK errors. Linear's GraphQL API returns errors in `response.errors[]` with `extensions.type` and `extensions.userPresentableMessage` fields. HTTP 200 responses can still contain partial errors -- always check the `errors` array. ## Prerequisites - Linear SDK or raw API access configured - Access to application logs - Understanding of GraphQL error response format ## Instructions ### Error Response Structure ```typescript // Linear GraphQL error shape interface LinearGraphQLResponse { data: Record<string, any> | null; errors?: Array<{ message: string; path?: string[]; extensions: { type: string; // "authentication_error", "forbidden", "ratelimited", etc. userPresentableMessage?: string; }; }>; } // SDK throws these typed errors import { LinearError, InvalidInputLinearError } from "@linear/sdk"; // LinearError includes: .status, .message, .type, .query, .variables // InvalidInputLinearError extends LinearError for mutation input errors ``` ### Error 1: Authentication Failures ```typescript // extensions.type: "authentication_error" // HTTP 401 or error in response.errors // Diagnostic check async function testAuth(): Promise<void> { try { const client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! }); const viewer = await client.viewer; console.log(`OK: ${viewer.name} (${viewer.email})`); } catch (error: any) ...