Overview

This node integrates with the Apify API to abort a specific run of an Actor. It is useful in scenarios where you need to stop an ongoing Actor execution, either immediately or gracefully, for example, to halt a web scraping task or data processing job that is no longer needed or needs to be restarted.

Use Case Examples

1. Abort a running Actor job by specifying the Actor ID and Run ID to stop unwanted or erroneous executions.
2. Gracefully abort an Actor run to allow it to save its state before stopping, useful for resuming later.

Properties

Name	Meaning
Actor ID	The unique identifier or a tilde-separated owner's username and Actor name to specify which Actor's run to abort. It supports selection from a list, URL input, or direct ID input.
Run ID	The unique identifier of the specific run of the Actor to abort. It supports selection from a list, URL input, or direct ID input.
Gracefully	Boolean flag indicating whether to abort the run gracefully, allowing the run to send aborting and persistState events and force-stop after 30 seconds. Defaults to true.
Use Custom Body	Boolean flag to specify whether to use a custom request body for the abort operation. Defaults to false.

Output

JSON

• status - The status of the abort operation response from the Apify API.
• data - Details of the aborted run returned by the Apify API.

Dependencies

• Apify API key credential for authentication

Troubleshooting

• Ensure the Actor ID and Run ID are valid and correctly formatted; invalid IDs will cause errors.
• If the run is already finished or does not exist, aborting will fail with an error.
• Network or authentication issues with the Apify API can cause request failures; verify API credentials and network connectivity.

Links

• Apify API - Abort Run - Official Apify API documentation for aborting an Actor run.