Fix: Prevent concurrent deployments by excluding main branch from check workflow #354
+4
−1
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.
Summary
Fixed deployment failures caused by concurrent workflow executions racing to deploy to the same CloudFormation stack.
Root Cause Analysis
The Problem
When PRs were merged to
main, bothauto-updateandcheckworkflows triggered simultaneously, causing race conditions:Why It Failed
2025-11-13T01:24:08Zon push to maindocker-selenium-lambda-prodUPDATE_ROLLBACK_COMPLETEstateWhy The Error Was Misleading
The error message suggested an ECR permission issue, but the real problem was the concurrent deployment race condition. The "permission denied" error was a side effect of CloudFormation being in an inconsistent state during the conflict.
Solution
Modified
check.ymlto excludemainbranch:Rationale:
auto-updateworkflow already handlesmainbranch deploymentscheckworkflow is now for feature branch validation onlyworkflow_dispatchfor manual testing when neededWorkflow Responsibilities
Test Plan
🤖 Generated with Claude Code