Fix deployment level concurrency - #183
Merged
leewujung merged 2 commits intoAug 23, 2026
Merged
Conversation
…y via work queue and deployment_concurrency that controls per-deployment concurrency
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR fixes the previous concurrency setting so that right now 2 levels of concurrency can be separately specified:
concurrency_groupgroups deployments and controls how many runs are executed within the associated work queue from all deployments specified in the same groupdeployment_concurrencycontrols if a new flow run would be cancelled (CANCEL_NEW) or queued (ENQUEUE) when the specified limit number of flow runs are already runningAlso added a README section to document the usage, which we can later move to the appropriate docs section in #170 .