Overview
The "Execution Orchestrator - Get Many" operation in this node allows users to retrieve multiple execution records from the Automation Anywhere platform. It is useful for scenarios where you want to list or query executions based on specific criteria, such as filtering by certain fields, limiting the number of results, and sorting the output.
Practical examples include:
- Fetching all executions that match a particular status or date range.
- Retrieving the latest 50 executions sorted by start time.
- Querying executions with custom filters to analyze performance or troubleshoot issues.
This operation helps automate monitoring and reporting workflows by programmatically accessing execution data.
Properties
| Name | Meaning |
|---|---|
| Filters | Conditions to filter the executions. Each condition includes: |
| - Condition Type: Equals, Greater, Greater or Equal, Less, Less or Equal, Not Equal | |
| - Field: Any searchable field name | |
| - Value: The value to compare against | |
| Limit | Maximum number of execution records to return (minimum 1). Default is 50. |
| Additional Fields | Extra options including: |
| - Sort | One or more sorting rules, each specifying: |
| - Direction: Ascending or Descending | |
| - Field: The field name to sort by |
Output
The node outputs an array of execution objects in the json property of the output items. Each object represents an execution record retrieved from the Automation Anywhere Execution Orchestrator API. The exact structure depends on the API response but typically includes details like execution ID, status, timestamps, and other metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for Automation Anywhere with appropriate permissions.
- The node communicates with the Automation Anywhere API endpoint specified in the credentials.
- No additional external dependencies are required beyond the configured API access.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Using invalid filter fields or operators may result in API errors or empty results.
- Requesting too many records without proper limits might lead to timeouts or rate limiting.
Error Messages:
- Authentication errors: Verify the API key and URL configuration.
- Validation errors on filters or sorting: Check that field names and operators are valid according to the Automation Anywhere API documentation.
- Rate limit exceeded: Reduce request frequency or limit the number of returned records.