Agent skill · data analytics · jeremylongshore
apify-common-errors
Diagnose and fix common Apify Actor and API errors. Use when an Apify run fails, an API call returns 401/403/404/413/429, a proxy connection drops, an Actor build breaks, or a scrape hits an anti-bot block, and you need the cause plus a copy-paste fix. Trigger with "apify error", "fix apify", "actor failed", "apify not working", "debug apify", "apify 429".
Why this skill is useful
Provides specific diagnostic commands and error handling patterns for Apify API errors that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq installed locally. Requires apify account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apify Common Errors Overview Quick diagnostic reference for the most common Apify errors. Covers Actor run failures, API errors, proxy problems, anti-bot blocks, and platform-specific issues. The full per-error catalog — raw signature, cause, diagnosis, and copy-paste fix for all ten errors — lives in references/error-reference.md; this file is the lean triage path that points you there. Prerequisites An Apify API token exported as APIFYTOKEN (Console > Settings > Integrations). Access to the Apify Console for reading run and build logs. curl and jq on PATH for the diagnostic commands below; apify CLI optional for build inspection. Instructions Work the failure from signal to fix: 1. Capture the exact error. Grab the Status / StatusMessage from the run, or the ApifyApiError message and HTTP code from the API response. The raw string is the key you match on. 2. Match the signature. Find the matching entry in the table below, then open references/error-reference.md at that number for the cause, diagnosis, and fix. 3. Diagnose before changing code. For run failures, pull the log via the API or Console (see the FAILED entry). For auth/rate/payload errors, the HTTP code already tells you the class — see Error Handling. 4. Apply the fix from the reference, re-run, and confirm with the diagnostic commands. Error signature → reference # Error Signature to match --- ------- -------------------- 1 Actor run FAILED Status: FAILED / exited with code 1 2 Actor run TIMED-OUT Actor timed out after N seconds 3 Rate limited Rate limit exceeded (429) 4 Unauthorized Authentication required (401) 5 Build failed Build failed: npm ERR! 6 Proxy connection failed 502 Bad Gateway / Could not connect to proxy 7 Anti-bot block status 403 / Captcha detected 8 Out of memory JavaScript heap out of memory 9 Dataset push too large Payload too large (413) 10 Actor not found Actor '…' not found (404) Full detail for every row: references/error-reference.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apify-common-errors