figma-advanced-troubleshooting

# Figma Advanced Troubleshooting ## Overview Deep debugging techniques for complex Figma REST API issues that resist standard error handling: intermittent failures, unexpected response shapes, rate limit edge cases, and large file timeouts. ## Prerequisites - Access to application logs - `curl` with verbose mode for network inspection - Figma API credentials for testing ## Instructions ### Step 1: Verbose Request Inspection ```bash # Full HTTP request/response trace for a Figma API call curl -v -H "X-Figma-Token: ${FIGMA_PAT}" \ "https://api.figma.com/v1/files/${FIGMA_FILE_KEY}?depth=1" 2>&1 \ | tee figma-debug-trace.txt # Extract key diagnostic info: # - TLS version and cipher # - Response status and headers # - Timing breakdown curl -w " DNS: %{time_namelookup}s Connect: %{time_connect}s TLS: %{time_appconnect}s TTFB: %{time_starttransfer}s Total: %{time_total}s Size: %{size_download} bytes Status: %{http_code} " -s -o /dev/null \ -H "X-Figma-Token: ${FIGMA_PAT}" \ "https://api.figma.com/v1/files/${FIGMA_FILE_KEY}?depth=1" ``` ### Step 2: Response Shape Validation ```typescript // Figma API responses can be unexpectedly shaped when: // - File is empty or newly created // - Nodes have been deleted between requests // - Plugin data is corrupted function validateFileResponse(data: any): string[] { const issues: string[] = []; if (!data.document) issues.push('Missing document root'); if (!data.document?.children?.lengt...