ISR pages are not regenerating on time

[yogeshydvme]

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.

App Id

d3iusqza06a1ll

Region

ap-south-1

Amplify Console feature

Not applicable

Describe the bug

We had multiple pages with revalidate 10, but for some reason the regeneration is not taking place. Sometime randomly it regenerates the pages, but sometime completely missed the regeneration.

We tried multiple timestamps like after 5sec, 10sec, 20sec but the behaviour is very inconsistent. Not sure why this is happening.

Expected behavior

Amplify should respect revalidate and make sure it either generates the page or provide error in cloudwatch if generation fails.

Reproduction steps

NA

Build Settings

No response

Additional information

No response

[swaminator]

@yogeshydvme what version of Next are you using?

[yogeshydvme]

@swaminator 10.2.3

[Athena96]

@yogeshydvme can you try with the latest version of next: next: 11.1.2 and the latest version of Amplify SSR (in the Build Settings, set the Next.js Version to latest: https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#update-app-nextjs-version)

[janajri]

I'm seeing a similar issue on my end. Our app id is: d1xm76k8s6lqms. I've set all revalidations to 1 minute and do not see the latest changes reflected after publishing our CMS / Contentful content. We've recently migrated away from Vercel into AWS directly, so I can verify that nothing has been changed during the migration.

[SatadruBhattacharjee]

+1, same issue with Nextjs 11 (with latest). ISR is not working. The same is working fine in Vercel

[SatadruBhattacharjee]

Any update on this ? it's kind of a BLOCKER

[ferdingler]

@SatadruBhattacharjee I'm sorry you are having issues. ISR should be working fine, can you check if your app meets the following requirements please?

• The app framework should be recognized as a NextJS -SSR app.
• There must be an IAM role assigned to your App

• This role needs to have either the AmplifyAdmin managed policy (arn:aws:iam::aws:policy/AdministratorAccess-Amplify), or these permissions.

• The NextJS version in the environment variables should be set to latest.

Can you confirm this is the case for your app? And if it is, and still doesn't work, what is the error that you get?

[SatadruBhattacharjee]

Hi @ferdingler,

Thanks for your message. Just to confirm the ISR is working fine now with the above mentioned recommendations. Thanks.

[yogeshydvme]

How to update regenration lambda timeout, by default it is assigning 10 sec and usually while generating page it times out. Please help.

[felixfirefighter]

Also having the same problem here. The timing of the regeneration is very inconsistent. Currently using next 11.1.2, _LIVE_UPDATES is also already set to latest.

Any help is appreciated.

[behrooziAWS]

@yogeshydvme Have you deployed your app after October 7th? The timeout was raised to 30 seconds which is the max. Are you still seeing it timeout after 10 seconds?

[behrooziAWS]

Actually, looks like the timeout is still set to 10s on the regeneration lambda even after our change to update it. It only took effect on other lambdas. Will investigate further.

[behrooziAWS]

We've identified the issue causing the regeneration lambda timeout to be limited to 10s, we will follow up when it has been addressed.

[yogeshydvme]

sure, it will be very helpful

[pogorsky]

Any updates on this issue?