Jay Raval

Hi @jefflutely 👋 , thanks for reaching out. Can you try the suggestions stated here: https://github.com/aws-amplify/amplify-hosting/issues/1004#issuecomment-1594014458? If you are still blocked, please let us know.

Thanks for confirming @jefflutely. As next steps, I'd recommend retrieving the logs for a shorter duration (less than a day) and will also suggest reaching out to [AWS support](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html#creating-a-support-case) if...

Hi @ferrivitor 👋 , thanks for reaching out. In scenarios where you need to change the repository associated with an existing AWS Amplify application, our general recommendation is to create...

Yes, its applicable to all Amplify apps (Gen 1 and 2).

@sasssssssa 👋 , thanks for reaching out. Currently, the deployments endpoint in the Amplify console is designed to point to the latest deployment. We will take this as a feature...

@cobalt88 👋 , thanks for reaching out to us. I was able to reproduce this behavior and marking this as a bug.

Hi @regularuserrr 👋 , thanks for reaching out. Have you reviewed your app's hosting compute logs? The logs are delivered to CloudWatch under the log group `/aws/amplify/{app-id}`. These logs should...

Closing this thread as we shared the best practice on debugging compute runtime errors.

Hi @syazwanz 👋 , thanks for raising this and for sharing detailed information about the issue. > If the build fail, my GitHub checks will get a message from Amplify...

Hi @monjurulbjit521 👋 , thanks for reaching out to us! I was able to reproduce a similar behavior while trying to preview the website URL (for a sample Next.js app)...