CI/CD build timed out with no error

[doraemoon-bot]

Before opening, please confirm:

• [X] I have checked to see if my question is addressed in the FAQ.
• [X] I have searched for duplicate or closed issues.
• [X] I have read the guide for submitting bug reports.
• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• [X] I have removed any sensitive information from my code snippets and submission.

App Id

d2efkxsw94m7n8

AWS Region

ap-northeast-1

Amplify Hosting feature

Backend builds

Describe the bug

The log output shows that the backend build completed successfully, but the build step is not complete. Front-end build did not start and the build timed out. This occurs when Lambda Resolver is committed. Just a couple of weeks ago I was able to do CI/CD builds with backend + frontend without any problems... Running amplify push locally completes successfully and works fine.

Expected behavior

Deployment ends successfully or logging detailed error messages.

Reproduction steps

1. Commit the Lambda resolver described in "Describe the bug"
2. Wait until build times out.

Build Settings

version: 1
backend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --simple --yes
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - yarn run build
  artifacts:
    baseDirectory: .next
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Log output

log.txt

Additional information

Uncheck "Enable full-stack continuous deployments (CI/CD)" in the Amplify console settings and skip the backend build, the CI/CD build will complete successfully.

[DiegoMcDipster]

This started happening yesterday. It seems to me to be related to the removal of permissions on lambda layers. And I'm not the only one. These are links to discord conversations on this: https://discord.com/channels/705853757799399426/1115774987396202516/1115774987396202516 & https://discord.com/channels/705853757799399426/1115648031283486821/1115648031283486821

my appId is d386awzddcslo4

[ColtG-py]

+1 also bit me today. Ended up tossing a lot of environments to fix this... would be great to hear from the Amplify team about this.

[DiegoMcDipster]

I can confirm switching off the CICD will allow the deployment to complete. But then the whole of the backend deployment step is skipped. So, it's not a solution.

[vorant94]

I'm having the same issue... the build literally takes 30 minutes for no reason and then fails

[Jay2113]

Hi everyone 👋 , the default build timeout is 30 mins. You can extend it up to 120 mins by setting the following environment variable on your Amplify app:

Variable: _BUILD_TIMEOUT 
Value: 120 mins

Over the past couple of years, we have also made improvements to our build logs to surface the appropriate errors.

[github-actions[bot]]

This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.

[github-actions[bot]]

This issue has been automatically locked.