We’re having multiple problems with whyfry-app. Sometimes the website doesn’t launch and gets stuck at “waiting for cache”. Sometimes the web app freezes mid usage with no errors. Sometimes the app doesn’t start a connection to our api, making it stuck on the loading screen. This happens like 10% …

hi there, could you try something for me? if you have asset optimization set to ON, could you turn it off and see if this fixes things? I know this isnt ideal permanently, but this may be an important clue as to what is happening here.

Hi Perry, Asset optimization was already disabled. It’s disabled on all our web apps.

We’re still having problems with our app on your platform. Our customers’ business are now in pure chaos. Building the app locally with production environments doesn’t give any issues. We tried to create a new app on your website, same results. We’re running out of options here, and might have t…

Creating a new app actually solved the problem it seems. But the strange thing is that the app doesn’t load via the domain name. A problem with a subdomain?

That sounds like a separate issue - what’s the API ID (or subdomain) of the new site and what is the name you are trying to access it by that doesn’t work (and in what way does it not work)? Once I can see that I’ll also be able to compare the difference between the two - to see if I can understand…

Hi, I created a new app in Netlify with ID whyfry-app, and renamed the older to whyfry-app-v1. This actually solved our problem. Apparently the dns records automatically changed to whyfry-app-v1 while the subdomain was linked in to whyfry-app in the domain settings of the app. Seems like another b…

solvengo, glad to see you saw improvement and i’m sorry it took us a bit to look at this. please do let us know if the problem resurfaces or more problems pop up.

[same problem] We’re having the same problem with other apps now. The loading page freezes, but tabs on the home page are partially loaded (hidden). Seems like only a part of our code is being served. whywaitt-app-dev seems to be affected as well, but our production whywaitt.com runs fine. Differ…

[bad gateway] We’re receiving 502 bad Gateway errors on all apps build after 29 March. Edit: Had 4 tabs open, all of them failed top loading resources. I honestly think this is a problem on your side. [new error]

Hey there, @solvengo :wave: Thanks so much for following up. I am sorry to hear that this issue has resurfaced! I have shared this thread and these details with our team, and they will look into this issue further for you. Stay tuned!

Frontend freezing, not loading, waiting for cache

Support

solvengo April 7, 2022, 10:29pm 21

Related Problem. We’re also having assets pending intermittently. Same behaviour in Chrome and Safari, while Firefox works correctly.

Topic		Replies	Views
Cache issue on Netlify? Support deployment	42	28698	January 6, 2025
(Very) slow loading of some js: TTBF / download / revalidation Support performance	30	3530	June 10, 2022
HTTP requests randomly stuck forever at pending on Chrome and Safari Support nextjs	8	19006	April 7, 2022
Netlify serve old cached version Support building , deployment , caching	41	7175	March 29, 2022
Local Build is working but Netlify Site gives chunk errors Support deployment	1	753	March 23, 2021

Frontend freezing, not loading, waiting for cache

Related topics