Overview
This node integrates with the Automation Anywhere API to manage executions within the Execution Orchestrator resource. Specifically, the "Stop" operation allows users to halt a running execution by specifying its unique execution ID. This is useful in scenarios where an automation process needs to be terminated prematurely due to errors, changed requirements, or manual intervention.
Practical examples include:
- Stopping a bot execution that is stuck or behaving unexpectedly.
- Halting scheduled automations during maintenance windows.
- Programmatically controlling execution flows based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Execution ID | The unique identifier of the execution to stop. This is a required string input. |
Output
The node outputs JSON data representing the response from the Automation Anywhere API after attempting to stop the specified execution. The exact structure depends on the API's response but typically includes status information about the stop request.
No binary data output is involved.
Dependencies
- Requires an active connection to the Automation Anywhere API.
- Needs an API authentication token or key configured in the node credentials.
- The base URL for the API is taken from the credential configuration and must be correctly set without trailing slashes.
Troubleshooting
- Invalid Execution ID: If the provided execution ID does not exist or is malformed, the API will likely return an error. Verify the execution ID before use.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key/token is valid and has sufficient permissions.
- Network Issues: Connectivity problems can prevent the node from reaching the Automation Anywhere API. Check network settings and firewall rules.
- API Rate Limits: Excessive requests may trigger rate limiting. Implement retries or backoff strategies if needed.
Common error messages might include unauthorized access, execution not found, or bad request errors. Resolving these involves checking credentials, verifying execution IDs, and ensuring correct API endpoint usage.