actor-run/getUserRunsList

When to Use

• Monthly billing reconciliation: At month-end, paginate through all runs in the account to aggregate compute usage across all actors. Use run IDs to fetch per-run costs via actor-run/get and produce an itemized billing report.
• Global failure detection: Filter by status: "FAILED" to get a cross-actor view of all recent failures. An ops dashboard can surface systemic issues (e.g. a proxy provider outage causing failures across multiple actors simultaneously).
• Usage governance: Track which actors are being run, how frequently, and at what cost — without knowing the full list of actor IDs in advance. Useful for enforcing Apify budget limits across teams sharing one account.
• Stuck run detection: Filter by status: "RUNNING" and identify runs with a startedAt timestamp older than your maximum expected run duration — possible indicators of frozen actors that need manual abort.
• Audit trail generation: For compliance or data governance purposes, retrieve and store a complete run ledger (all actors, all statuses) on a daily or weekly schedule to maintain a durable history beyond Apify's own retention period.

Configuration

Connection

Operation

Sample Configuration

{
  "resource": "actor-run",
  "operation": "get-user-runs-list",
  "credentialId": "apify-admin-token",
  "status": "FAILED",
  "offset": "0",
  "limit": "50",
  "desc": "true"
}

Validation Errors

Output

Success Port

Run summary object fields:

Error Port

Routes here when authentication fails or a network error occurs. Output contains errorCode ("APIFY_ERROR") and message.

Sample Output

{
  "runs": [
    {
      "runId": "run_x1y2z3",
      "actorId": "apify~web-scraper",
      "status": "FAILED",
      "startedAt": "2026-05-26T11:30:00.000Z",
      "finishedAt": "2026-05-26T11:30:45.000Z"
    },
    {
      "runId": "run_a4b5c6",
      "actorId": "my-org~price-monitor",
      "status": "FAILED",
      "startedAt": "2026-05-26T11:00:00.000Z",
      "finishedAt": "2026-05-26T11:01:12.000Z"
    }
  ],
  "count": 2,
  "offset": 0,
  "limit": 50
}

Expression Reference

Node Policies & GuardRails

Examples

Global Failure Alert — Cross-Actor Health Check

{
  "resource": "actor-run",
  "operation": "get-user-runs-list",
  "credentialId": "apify-admin-token",
  "status": "FAILED",
  "offset": "0",
  "limit": "20",
  "desc": "true"
}

Runs every 30 minutes. An IfCondition checks {{ $output.apify.count }} > 0. If failures are detected, a CollectionOperation node extracts the distinct actorId values and a Slack node posts a summary: "2 failed runs detected across actors: apify~web-scraper, my-org~price-monitor."

Monthly Usage Report — Full Account Pagination

// Loop node (max 100 iterations, variable: pageOffset starts at 0)
{
  "resource": "actor-run",
  "operation": "get-user-runs-list",
  "credentialId": "apify-admin-token",
  "status": "SUCCEEDED",
  "offset": "{{ $variables.pageOffset }}",
  "limit": "100",
  "desc": "false"
}
// After each iteration: pageOffset += 100
// Accumulate all runs into a variable array
// Break when count < 100

Retrieves all successful runs for the month in chronological order. The accumulated run IDs are passed to a batch actor-run/get loop that fetches cost data (usageTotalUsd) for each run, then groups by actorId to produce a per-actor cost breakdown report.

Stuck Run Detection — Running Longer Than 2 Hours

{
  "resource": "actor-run",
  "operation": "get-user-runs-list",
  "credentialId": "apify-admin-token",
  "status": "RUNNING",
  "offset": "0",
  "limit": "50",
  "desc": "true"
}
// Downstream: Function node filters runs where:
// (now - startedAt) > 7200 seconds (2 hours)
// Alert on any stuck runs

A Function node downstream calculates run duration for each item in the runs array and filters those running for more than 2 hours. An alerting node sends an operations notification with the stuck run IDs for manual investigation or abort.