- Introduction
- Getting started
- Process modeling
- Process implementation
- Debugging
- Simulating
- Publishing and upgrading agentic processes
- Common implementation scenarios
- Extracting and validating documents
- Process operations
- Process monitoring
- Process optimization
- Reference information
Maestro user guide
Overview
Instance throttling is a temporary performance adjustment that Maestro applies when a workflow instance generates an unusually high volume of activity in a short period. This mechanism ensures fair resource distribution across all workflows and maintains platform stability.
When throttling is active, your workflow continues to run without interruption — it may just take longer than usual to complete. Performance returns to normal automatically as activity volume decreases.
What causes throttling
Throttling activates when a single workflow instance executes a high number of activities within a short time window. Common scenarios include:
- Large batch processing: A workflow processing thousands of items in rapid succession.
- Tight loops: Workflow logic that repeatedly executes activities without delays.
- Parallel execution: Multiple branches executing many activities simultaneously.
- High-frequency integrations: Rapid API calls or data operations in a loop.
Throttling is not an error condition — it is a normal platform behavior designed to prevent any single workflow from consuming excessive resources.
Throttling indicators in the console
Maestro shows a warning indicator when a running instance is throttled:
- Instances table: A ⚠ warning icon appears next to the instance status. Hovering shows the tooltip: Instance is throttled due to high activity volume.
- Instance details page: A warning banner appears at the top of the page: This instance is being throttled due to high activity volume. Execution continues at reduced speed.
The indicator reflects the real-time throttling state and updates within seconds of each activity completing. It disappears automatically once the instance is no longer throttled. Because throttling is transient, there is no historical record or filter for past throttling events.
What to expect when throttled
| Aspect | Behavior |
|---|---|
| Workflow execution | Continues running without interruption |
| Activity processing | Executes at a reduced rate |
| Data integrity | Fully preserved — no data loss or corruption |
| Completion | Workflow completes normally, just takes longer |
| Recovery | Automatic — performance returns to normal as activity volume decreases |
No action is required. Throttling is temporary and self-resolving.
Optimizing workflows that throttle frequently
While no action is required, you can reduce how often throttling occurs:
Reduce activity frequency
- Add small delays between iterations when processing speed is not critical.
- Batch multiple operations into single activities where possible.
- Use asynchronous patterns for non-urgent processing.
Distribute workload
- Split large batches across multiple workflow instances.
- Schedule batch processing during off-peak hours when possible.
- Use queue-based patterns to naturally pace work distribution.
Review workflow design
- Evaluate whether all activities are necessary for each iteration.
- Consider consolidating repeated similar operations.
- Review loop structures for optimization opportunities.
Frequently asked questions
Does throttling affect my workflow results? No. Throttling only affects execution speed, not the outcome. All activities execute completely, all data is preserved, and your workflow produces the same results as it would without throttling.
Will my workflow time out while throttled? Throttling does not change timeout configurations. If your workflow has custom timeouts shorter than the throttled execution time, you may need to adjust them. Default platform timeouts account for throttled execution.
Can I disable throttling for my workflow? Throttling is a platform-level protection that cannot be disabled for individual workflows. If you have specific high-throughput requirements, contact UiPath support to discuss your use case.
How long does throttling last? Throttling duration depends on your workflow's activity pattern. As soon as the activity rate decreases to normal levels, throttling lifts automatically — typically within seconds to minutes.
Does throttling affect other workflows? No. Throttling is applied per instance. Other workflow instances, including other instances of the same process, run independently at their normal speed.
Why was my workflow throttled when it ran fine before? Several factors can influence throttling: changes in input data volume, workflow modifications that increased activity count, platform-wide load conditions, or concurrent execution with other high-volume instances.