Overview
The node provides integration with the Automation Anywhere platform, specifically focusing on managing executions within the "Execution Orchestrator" resource. The "Archive" operation allows users to archive one or more executions by their IDs. This is useful for cleaning up or organizing execution records after they have completed or are no longer needed in active views.
Practical scenarios include:
- Archiving finished automation runs to keep the execution list manageable.
- Automating cleanup of old executions as part of a maintenance workflow.
- Organizing executions by archiving those that meet certain criteria (e.g., status, age).
Properties
| Name | Meaning |
|---|---|
| Execution ID | The unique identifier of the execution to archive. This is a required string input. |
Output
The node outputs JSON data representing the response from the Automation Anywhere API after attempting to archive the specified execution(s). The exact structure depends on the API response but typically includes confirmation of success or details about any errors encountered.
No binary data output is indicated.
Dependencies
- Requires an API key credential for Automation Anywhere with appropriate permissions.
- Needs the base URL of the Automation Anywhere API instance configured in credentials.
- Uses internal helper functions to make authenticated HTTP POST requests to the Automation Anywhere API endpoints.
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 is correct and exists.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to archive executions.
- Network Issues: Connectivity problems to the Automation Anywhere API endpoint can cause failures. Check network access and API availability.
- API Rate Limits: Excessive requests may be throttled; consider adding delays or retries if encountering rate limit errors.