We’re trying to access our pricing management app (pgCeniky) in Retool. The expected behavior is that the app loads and all queries and components initialize properly so we can manage product pricing.
That is always frustrating when nothing loads. Let's try a few things to see if we can get it going again. You may have gone through some of these but here's a little list to help:
Open the Debug Area. At the bottom of the Retool editor, find and click Debug (bottom toolbar). Look for: Errors or warnings in the query logs.
Inspect Queries in Debug Mode. Check the status of each query. Look for queries with the status "Loading", "Queued," or stuck in "Running."
Use "Edit App" to isolate issues. In the editor, click the Edit App button (top-right corner): Attempt to temporarily disable queries: Open the problematic query. Uncheck "Run query automatically when inputs change" or "Run query on page load."
Diagnose Circular Dependencies. Open the Retool editor in a different browser (Chrome incognito is best). Append ?_historyOffset=-1 to your app URL to load a previous stable state: https://akinu.retool.com/editor/ceniky/pgCeniky?_historyOffset=-1
Inspect and Pause Queries on Load. In the Retool editor URL, use ?_disableQueryOnPageLoad=true to load the app with all queries disabled: https://akinu.retool.com/editor/ceniky/pgCeniky?_disableQueryOnPageLoad=true.
Validate DB & API Resources. Navigate to the Retool resource page and test all database/API resources separately to confirm connectivity. Go to Resources → Your DB/API → Test Connection.
Join the Retool team and community at office hours! Today 11am-12pm PST. It is a great way to solve any issues live or via message. It is also a great way to see who is doing what and see how others solve issues.
Hope this helps! Let me know how it goes and we can further debug.,
Do you have any modules integrated? This can be a source of slowing apps to a halt. If so try going into each module to look for issues. Also, once the main app opens, you can try deleting all of the modules, then adding them one by one.
Is this a single page app (legacy) or a multi-page app? I would export to JSON then create a new app from the JSON file.
Screenshots of your debug window (even if blank) as well as your component tree and cose/resources would help.
Yes, I’m using one module – for navigation – exactly the same one used in our other working apps. I tried removing it, but it didn’t help.
It’s a multi-page app. I tried exporting the app to JSON and creating a new one from it, but it failed with an internal server error. I also noticed there’s an incident reported on https://status.retool.com/ which might be related.
Regarding the “snippet of code/resources” – could you clarify what exactly you mean? The queries don’t run at all, and nothing is triggered, so I’m not sure what snippet would be helpful here.
I just watched the video and it does seem strange. Regarding “snippet of code/resources” the video helped. I just wanted to see the number and types of queries, etc.
Do you have time to jump on the Office Hours? It starts in 15 minutes. The Retool team is really good and I can try to make it.
I brought up your issue in office hours and @Tess mentioned there is an incident the engineers are currently working on. Hopefully this will resolve the issue shortly.
I also just received the email below. I am guessing this is your culprit.
Unfortunately, the issue still persists on our side – the app loads eventually but remains completely unresponsive. Queries don’t run, and the UI is frozen just like before.
Do you have any estimate on how long we should wait before it’s fully resolved? We rely on this app daily, so any guidance would be appreciated.
Thank you, @Shawn_Optipath, for flagging this in office hours!
We updated the status page to better reflect the ongoing incident (we are investigating source control issues and app loading issues).
We're working on sending out a fix this afternoon. We are still working on sorting out the root cause, but the fix should resolve the various loading/performance issues affected apps suddenly started seeing. Once you see version 3.176 in the help ? menu on the bottom right corner of the editor, the fix should be included:
