#✅ - Build failed to complete successfully. Reason: Build timed out

1 messages · Page 1 of 1 (latest)

smoky crest
#

I'm getting this message when i try to run a build (via git push & via console deploy). On the build log for the backend it's processes to a certain point and just stops and waits. 2023-06-05T16:54:18.503Z [INFO]: When I look at cloudformation I see that it's trying to delete a lambadalayer permission for two hours and then returns DELETE FAILED. Resource timed out waiting for completion (RequestToken: ###-###)

Can someone please advise what I should look at to dig further into this please? For example, i have the RequestToken. But how can I utilise this to help with debugging?

I suspect it's something to do with permissions for older versions of the lambda layer but that is really clutching at straws. I'm lost on what to do with this.

Note, amplify push worked fine, local build is also fine.

Any tips would be much appreciated

#

Note, the last successful build I had was on 31-May. If I try to redeploy that build now though, I get the same issue.

coarse peak
#

Hi @smoky crest 👋 , apologies for the delayed response on this thread. Please refer to my comment on this GitHub issue: https://github.com/aws-amplify/amplify-hosting/issues/2751#issuecomment-1589807105 as it provides detailed insights on the root cause of this issue and some workarounds that you could leverage to unblock your builds 🙂

GitHub

Before opening, please confirm: I have checked to see if my question is addressed in the FAQ. I have searched for duplicate or closed issues. I have read the guide for submitting bug reports. I hav...

mint nightBOT
#

✅ - Build failed to complete successfully. Reason: Build timed out