("ResourceConflictException") build causes 503's - handle build failures gracefully
See original GitHub issueOn the theme of handling build failures gracefully – I encountered this errors today which caused my site to 503.
The operation cannot be performed at this time. An update is in progress for resource: arn:aws:lambda:XXX
Also – Shouldn’t a build give a non-zero exit code? My CI pipeline thought this passed because no error code was given, which made this even harder to catch.
Issue Summary
Build failures should not break site
Actual behavior
Build failures break site
Versions
- OS/Environment: MacOS
- @sls-next/serverless-component version: @sls-next/serverless-component@v3.5.0-alpha.8
- Next.js version: ^10.2.4-canary.2
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:6
Top Results From Across the Web
AWS lambda ResourceConflictException on deployment
When I do that locally, it fails when deploying the environment, on jenkins it always fails when deploying the code. I'm not sure...
Read more >Error handling in Step Functions - AWS Documentation
A States.Runtime error isn't retriable, and will always cause the execution to fail. A retry or catch on States.ALL won't catch States.Runtime errors....
Read more >An update is in progress for resource - AWS re:Post
After deploying (update) a Lambda for about 150 times in an automated way using CI, this suddenly fails since in `eu-west-1` since 2021-09-14...
Read more >Troubleshooting App Thinning and Bitcode Build Failures
Workaround: Fix Info.plist files to stop referring to missing executables. Failure handling apps where the CFBundleSupportedPlatforms key in an ...
Read more >Troubleshooting Unexplained Build Failures - CircleCI
Things to check when your build has failed.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop 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
Top GitHub Comments
Update: Fixed it by updating per this thread #1976. Still scary to have deploys randomly start failing though… can we mitigate this?
Is it safe to update a NextJS 9 app using
@sls-next/serverless-component@1.18.0
to the latest release (3.6.0
) that includes this fix?