Overview
This node integrates with the Automation Anywhere API, specifically focusing on managing executions within the Execution Orchestrator resource. The "Resume" operation allows users to resume a previously paused execution by specifying its unique execution ID. This is useful in automation workflows where an execution was intentionally paused and needs to be continued without restarting from scratch.
Practical examples include:
- Resuming a robotic process automation (RPA) task that was paused due to manual intervention or system conditions.
- Automating recovery steps in a workflow by resuming halted executions programmatically.
Properties
| Name | Meaning |
|---|---|
| Execution ID | The unique identifier of the execution to resume. This is required to specify which paused execution should be resumed. |
Output
The node outputs JSON data representing the response from the Automation Anywhere API after attempting to resume the specified execution. This typically includes status information about the resumed execution, such as confirmation of the action or any relevant metadata returned by the API.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Automation Anywhere API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for the API must be set correctly in the credentials configuration.
- The node uses POST requests to interact with the API endpoints.
Troubleshooting
Common issues:
- Invalid or missing Execution ID: The node requires a valid execution ID; providing an incorrect or empty value will cause the operation to fail.
- Authentication errors: If the API key or token is invalid or expired, the request will be rejected.
- Network connectivity problems: Failure to reach the Automation Anywhere API endpoint will result in errors.
Error messages and resolutions:
- "Execution ID is required": Ensure the Execution ID property is filled with a valid string.
- "Unauthorized" or "Authentication failed": Verify that the API credentials are correct and have not expired.
- "Execution not found": Confirm that the provided Execution ID corresponds to an existing paused execution.
- Timeout or network errors: Check internet connectivity and API endpoint availability.