Troubleshoot common Apify Actor and API failures by matching the exact error signature to a catalog entry. Get likely causes, copyable fixes, and commands to verify recovery for authentication, rate limits, builds, proxies, payloads, and anti-bot blocks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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".
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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.
APIFY_TOKEN (Console > Settings > Integrations).curl and jq on PATH for the diagnostic commands below; apify CLI optional for build inspection.Work the failure from signal to fix:
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.| # | 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.
Working through this skill yields:
SUCCEEDED, valid username, etc.).| HTTP Code | Meaning | Retryable | Action |
|---|---|---|---|
| 400 | Bad request | No | Fix input/params |
| 401 | Unauthorized | No | Check token |
| 403 | Forbidden | No | Check permissions |
| 404 | Not found | No | Verify resource ID |
| 408 | Timeout | Yes | Retry with backoff |
| 413 | Payload too large | No | Reduce batch size |
| 429 | Rate limited | Yes | Auto-retried by client |
| 500+ | Server error | Yes | Auto-retried by client |
Diagnostic commands for the most common triage steps:
# Check Apify platform status
curl -s https://api.apify.com/v2/health | jq '.'
# Verify your auth (fixes 401 diagnosis)
curl -s -H "Authorization: Bearer $APIFY_TOKEN" \
https://api.apify.com/v2/users/me | jq '.data.username'
# Check installed package versions
npm list apify-client apify crawlee 2>/dev/null
# Get last run status (find why a run FAILED / TIMED-OUT)
curl -s -H "Authorization: Bearer $APIFY_TOKEN" \
"https://api.apify.com/v2/acts/USER~ACTOR/runs?limit=1&desc=true" | \
jq '.data.items[0] | {status, statusMessage, startedAt, finishedAt}'
For the worked fix behind each error — e.g. reading a run log to find a stack trace, batching dataset pushes under 9MB, or switching to residential proxies to clear a 403 — see the matching entry in references/error-reference.md.
For comprehensive multi-error debugging across a whole Actor project — log
correlation, proxy rotation strategy, and build-cache issues — see the
apify-debug-bundle skill in this pack.
</content>
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.