Index of every page on this site: llms.txt
All skills
Run it yourself

Collect Apify debug evidence for support tickets and troubleshooting. Use when an Actor run has failed, is stuck, or produced empty output and you need to gather run metadata, logs, dataset samples, and environment info before opening a support ticket. Trigger with "apify debug", "apify support bundle", "collect apify logs", "apify diagnostic", "apify run failed why".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/apify-debug-bundle

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesexamples.md

≈589 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Apify Debug Bundle — Worked Examples

End-to-end walkthroughs showing the debug-bundle workflow applied to real failure scenarios. Each example maps to a step in implementation.md.

Example 1: A run that finished with status FAILED

You have a run ID (abc123DEF) that ended in failure and you want the full picture before opening a ticket.

export APIFY_TOKEN="apify_api_..."
./apify-debug-bundle.sh abc123DEF
# → Collecting debug info for run abc123DEF...
# → Bundle created: apify-debug-20260717-142530.tar.gz
# → Attach this file to your Apify support ticket.

Unpack and inspect the tail of the log to find the stack trace:

tar -xzf apify-debug-20260717-142530.tar.gz
tail -40 apify-debug-20260717-142530/run-log.txt

Example 2: "It worked yesterday" — compare against a good run

The Actor succeeded last run but fails now with the same input. Diff the two to surface what changed (build number, memory, timeout, request stats):

await compareRuns('goodRun789', 'badRun456');
// === Run Comparison ===
// Field                     | Success         | Failed
// ------------------------------------------------------------
// status                    | SUCCEEDED       | FAILED <--
// buildNumber               | 0.1.7           | 0.1.8 <--
// options.memoryMbytes      | 2048            | 2048
// stats.requestsFailed      | 0               | 143 <--

The <-- markers point straight at the regression: a new build (0.1.8) that now fails 143 requests.

Example 3: Empty dataset investigation

The run reports SUCCEEDED but produced zero items. Pull the run summary and dataset stats with the SDK:

const { run } = await investigateRun('emptyRun321');
// Dataset items: 0

Zero items on a successful run points at the Actor's own logic — check the failedRequestHandler in the Actor code (see the Error Handling table in SKILL.md).

Example 4: Live-tailing a hung run

A run has been RUNNING far longer than expected and the final log is not yet available. Stream it live instead:

RUN_ID="hangingRun999" ./tail-log.sh
# ...streams log lines every 2s until you Ctrl-C...

Watch for the last line before the stall — repeated retry/timeout lines usually indicate a proxy or target-site block rather than an Actor bug.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill is a diagnostic utility designed to collect Apify Actor run information, logs, and metadata for troubleshooting and support. It includes built-in redaction for local environment variables and uses official Apify API endpoints, though it possesses a surface for indirect prompt injection via external log data.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 months ago
What it can do
Reads files Runs commands
version
1.5.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "saas",
  "scraping",
  "automation",
  "apify"
]
All 7 allowed tools
ReadBash(curl:*)Bash(npm:*)Bash(node:*)Bash(tar:*)Bash(apify:*)Grep
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/apify-debug-bundle