- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Automation Suite Robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Orchestrator testing
- Integrations
- Troubleshooting

Orchestrator user guide
Editing Transactions
linkFrom the Transactions window you can edit the details of an individual queue item, or clone that item entirely. This is helpful for changing the priority or deadline of a transaction to respond to business needs, or editing the data input for failed transactions before retrying them.
Editing a Transaction
linkTo edit an individual queue item, follow these steps:
- Click the More Actions button for the desired transaction. The More Actions menu appears.
- Select Edit. The Edit queue item window is displayed.
- The editable fields and their descriptions are:
Field
Description
Transaction priority
The processing priority level of the transaction, can be set to Low,Normal, or High.
The priority is only editable for queues with disabled SLA predictions. If SLA predictions are enabled, the priority is set to High by default.
Postpone date and time
Enter the earliest date and time at which the transaction is available for processing.
This ensures that a queue item is not executed prior to the set timestamp.
Deadline date and time
Enter the latest date and time at which the transaction should be processed.
This is helpful when having to select between several items with the same priority.
Specific data
Select download as JSON to obtain a file of the transaction item's specific data, for review and editing. The edited file, or an entirely new one, can replace the current transaction data via the upload JSON and override button.
Note: The file cannot contain any arrays.Transaction progress
Populated according to the progress property defined in Studio. You can Keep transaction progress as is, or Reset transaction progress by selecting the corresponding radio button.
- Click Save to apply your edits to the transaction.
Cloning a Transaction
linkTo clone an individual queue item, follow these steps:
- Click the More Actions button for the desired transaction. The More Actions menu appears.
- Select Clone. The Clone queue item window is displayed.
- The editable fields and their descriptions are:
Field
Description
Transaction Reference
A unique identifier for the queue item. This key can be used in Elasticsearch to look for a specific item and view its logs.
Transaction priority
The processing priority level of the transaction, can be set to Low,Normal, or High.
The priority is only editable for queues with disabled SLA predictions. If SLA predictions are enabled, the priority is set to High by default.
Postpone date and time
Enter the earliest date and time at which the transaction is available for processing.
Deadline date and time
Enter the latest date and time at which the transaction should be processed.
Specific data
Select download as JSON to obtain a file of the transaction item's specific data, for review and editing. The edited file, or an entirely new one, can replace the current transaction data via the upload JSON and override button.
Note:- The file cannot contain any arrays.
- Back slashes are not supported.
- Click Create Queue Item to save the cloned transaction.