Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Limit the number of actions per orchestration
See original GitHub issuePerformance of orchestrations can drop significantly if an instance has too large of a history. For that reason, we should limit the maximum number of actions a single orchestration instance can make. If more actions are needed, users can break their large orchestrations into sub-orchestrations or use ContinueAsNew to limit the size of their history.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Setting MaxOrchestrationActions in an Azure Durable ...
Maximum amount of orchestration actions 100,000 has been reached. This value can be configured in host.json file as MaxOrchestrationActions.
Read more >Performance and scale in Durable Functions - Azure
These settings control the maximum number of orchestrator, entity, or activity functions that are loaded into memory on a single worker. Note.
Read more >Azure Storage provider for Durable Functions
There's no practical maximum number of total orchestrations or entities that can run on a single VM, even if they're all in the...
Read more >General Flow Orchestration Limits
When using orchestrations, keep orchestration limits, flow limits, and Apex governor limits in mind.Required Editions Available in: Lightning Experience A..
Read more >Studio - Orchestration Process
Implement an appropriate batching in workflows that expect a high number of actions per job. Please note that there is a default limit...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@SimonLuckenuik Yes! My PR referenced above does make the value configurable, just defaulted to 100k. The variable is MaxOrchestrationActions and can be changed in the host.json.
@cgillum did you happen to have any numbers to share for this issue? Does this tie into the size of DurableFunctionsHubHistory in storage? Attempting to diagnose why a large number of orchestrations (that then call numerous sub orchestations) is having low throughput.