Overview

This node interacts with the Apify API to retrieve a list of runs for a specified Actor. It is useful for users who want to monitor or analyze the execution history of their Apify Actors, such as checking recent runs, filtering runs by status, or paginating through run data. For example, a user can fetch the last 100 successful runs of a particular Actor to analyze performance or debug issues.

Use Case Examples

1. Fetch the last 50 successful runs of an Actor to monitor its recent activity.
2. Retrieve runs starting from an offset to paginate through historical run data.
3. Filter runs by status to get only failed or running executions for troubleshooting.

Properties

Name	Meaning
Actor ID	The unique identifier or a tilde-separated owner's username and Actor name to specify which Actor's runs to retrieve. It supports selection from a list, direct URL input, or manual ID entry.
Offset	Number of runs to skip from the start, used for pagination. Default is 0.
Limit	Maximum number of runs to return, with a default and maximum of 1000.
Desc	Boolean flag to sort runs by their start time in descending order if true; ascending order if false.
Status	Filter runs by their status, such as SUCCEEDED, to return only runs matching the specified lifecycle state.
Use Custom Body	Option to use a custom request body instead of default query parameters.

Output

JSON

• runs - Array of run objects for the specified Actor, each containing details about individual runs such as status, start time, and other metadata.

Dependencies

• Requires Apify API credentials for authentication.

Troubleshooting

• Ensure the Actor ID is valid and correctly formatted; invalid IDs or URLs will cause errors.
• Check API credentials are correctly configured to avoid authentication failures.
• If no runs are returned, verify the status filter and pagination parameters are set correctly.

Links

• Apify Actor Run Statuses - Documentation on available run statuses to filter runs.