Not able to see fallback using suspense

[turbid smelt]

Hi @quick cliff. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

Based on the knowledge sources provided, it seems that there are some issues with Suspense in Next.js when used in production or in certain deployment environments.

In one of the issues discussed on GitHub, a user reported that Suspense in production was blocking rather than showing the fallback UI. The issue was observed when the application was deployed on an AWS Amplify or EC2 server. The fallback UI didn't appear on the client side, instead, it waited for the complete UI to load. This issue didn't occur in the development environment or when running a local build. However, some users reported that disabling buffering in Nginx configuration fixed the issue for them (source (https://github.com/vercel/next.js/issues/54667)).

In another issue, it was reported that the Suspense fallback was not being displayed when updating query parameters and having multiple Suspenses on a single page. The fallback was not shown when the button was clicked and the query parameter only updated in the URL after the loading. However, if there was only one Suspense component on the page, the fallback worked as expected (source (https://github.com/vercel/next.js/issues/62049)).

If you're facing similar issues, you might want to check your deployment environment and configuration, or consider the number and usage of Suspense components on your page. If the issue persists, it might be a good idea to report it on the Next.js GitHub page, providing as much detail as possible about your setup and the issue you're experiencing.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

@quick cliff kapa.ai is still learning and improving, please let us know how it did by reacting below