#✅ - Pipeline failing every second time

10 messages · Page 1 of 1 (latest)

tropic jetty
#

Hi brains! After adding social providers (google & apple) my pipeline fails inconsistently. I need to keep re-triggering (without any changes) until it actually passes.

I have created my application on the very early days of Gen2 - not sure if that is related... That being said, I've been keep very up tp date with the new changes...

Cause: ❌ Deployment failed: Error: The stack named amplify-xxxxxx-staging-branch-xxxx failed to deploy: UPDATE_ROLLBACK_COMPLETE: Received response status [FAILED] from custom resource. Message returned: TimeoutError: {"state":"TIMEOUT","reason":"Waiter has timed out"}

coral wagon
tropic jetty
#

For reference I'm currently using:

"@aws-amplify/backend": "^1.0.4",
"@aws-amplify/backend-cli": "^1.2.0",
tropic jetty
#

Any inputs on this?!

severe arrow
burnt thicket
narrow forgeBOT
#

✅ - Pipeline failing every second time

#

Marked as solved.

brittle arch
#

This exact issue still happening with

"@aws-amplify/backend": "^1.1.1",
"@aws-amplify/backend-cli": "^1.2.3",
brittle arch
#

This is finally solved.

For me, the issue was the "concurrent executions" in https://us-west-1.console.aws.amazon.com/servicequotas/home/services/lambda/quotas (change for your region).

For new accounts, "concurrent executions" is 10 and not 1000 - at least, that was the case for me. I think this was a bug at some point, took a while to find this one!

To resolve, you need to submit a request to AWS to up you to the default of 1000. After that, no issues deploying 🎉