Support custom priority on orchestration workitem dispatching #498
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change introduces customer-defined orchestration dispatch priority
It allows customers to assign a priority value to orchestration instances so that higher-priority work items are dispatched earlier when multiple orchestration runs are competing for execution.
This mechanism affects dispatch ordering, not completion order.
While higher-priority instances are more likely to be picked up and started first, completion time is not guaranteed, as execution duration varies per orchestration and multiple work items are processed concurrently across workers.