Summary
On public app links (/p/...), a classic app opened in a new browser tab intermittently hangs forever on the loading spinner because Retool's bundled React Router RouterProvider misses the router's 'initialized' state update (a timing-dependent lost-update race), leaving the HydrateFallback spinner on screen before any app code runs.
AI Response
This matches an actively tracked issue where public/embedded classic apps intermittently get stuck on the infinite loading spinner before the runtime executes any queries, with the frequency tied to the local browser environment (notably new windows/tabs in Chrome). A refresh is the current interim workaround, consistent with the F5 behavior already observed. Retool staff traced a major contributor to service worker page caching and shipped fixes (June 10, June 17, and an additional reliability fix on Aug 30, 2026); a partial mitigation is to disable the 'Cache Service Worker' beta setting in Org Settings and then manually unregister the service worker via DevTools. Note that some reporters still saw occasional hangs after these changes, which aligns with this being a residual timing race rather than a fully closed issue.
Sources
Application not loading for certain users
Directly corroborates the same symptom—public-facing classic apps stuck on an infinite spinner before queries run, more likely in a new window/tab—and documents Retool's investigation, the service-worker-cache root cause, shipped fixes, and the disable-Cache-Service-Worker workaround.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a 
, 
, or 
. Or by marking this post as the "Solution"! Let us know if you have any feedback here. 