You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2025. It is now read-only.
The hasISRPages flag in the Deployment flow is based on the NonDynamicSSG in the manifest.
however, triggerStaticRegeneration() will be called if 'revalidate' is setted even for DynamicSSG-only pages.
CloudFront returns 503 error page because there is no dependent SQS resource and regeneration-handler function
Actual behavior
503 ERROR
The request could not be satisfied.
The Lambda function associated with the CloudFront distribution is invalid or doesn't have the required permissions. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Expected behavior
ISR should work with my component
Steps to reproduce
I have created and tested the following Page component.
At this time, the default-handler of CloudWatch Logs had the following output.
{
"errorType": "AWS.SimpleQueueService.NonExistentQueue",
"errorMessage": "The specified queue does not exist for this wsdl version.",
"Type": "Sender",
"Code": "AWS.SimpleQueueService.NonExistentQueue",
"Detail": "",
"name": "AWS.SimpleQueueService.NonExistentQueue",
"$fault": "client",
"$metadata": {
"httpStatusCode": 400,
"requestId": "6a0ae010-953f-55e7-9b33-b96fe51a7531",
"attempts": 1,
"totalRetryDelay": 0
},
"stack": [
"AWS.SimpleQueueService.NonExistentQueue: The specified queue does not exist for this wsdl version.",
" at /var/task/index-94ce7346.js:2068:68",
" at step (/var/task/serdePlugin-6d615471.js:91:23)",
" at Object.next (/var/task/serdePlugin-6d615471.js:72:53)",
" at fulfilled (/var/task/serdePlugin-6d615471.js:62:58)",
" at processTicksAndRejections (internal/process/task_queues.js:95:5)"
]
}
You have reviewed the README and FAQs, which answers several common questions.
You have reviewed our DEBUGGING wiki and have tried your best to include complete information and reproduction steps (including your configuration) as is possible.
You have first tried using the most recent latest or alpha@sls-next/serverless-componentrelease version, which may have already fixed your issue or implemented the feature you are trying to use. Note that the old serverless-next.js component and the serverless-next.js plugin are deprecated and no longer maintained.
Issue Summary
hasISRPages
flag in the Deployment flow is based on the NonDynamicSSG in the manifest.triggerStaticRegeneration()
will be called if 'revalidate' is setted even for DynamicSSG-only pages.regeneration-handler
functionActual behavior
Expected behavior
ISR should work with my component
Steps to reproduce
I have created and tested the following Page component.
Screenshots/Code/Configuration/Logs
It reminded of me the problem reported at #1098.
At this time, the
default-handler
of CloudWatch Logs had the following output.Versions
Additional context
point of
serverless-next.js/packages/serverless-components/nextjs-component/src/component.ts
Line 447 in b5d03b1
$ jq . < .serverless_nextjs/default-lambda/manifest.json
Checklist
latest
oralpha
@sls-next/serverless-component
release version, which may have already fixed your issue or implemented the feature you are trying to use. Note that the oldserverless-next.js
component and theserverless-next.js
plugin are deprecated and no longer maintained.Workaround
Add one dummy path of any kind and deploy again.
The text was updated successfully, but these errors were encountered: