Since yesterday, I've been trying to edit my apps in Retool, but when I try to save the queries, they keep loading endlessly and don't save. This happens on both mobile and desktop, as I show in the video below:
1 Like
all I can say is that I noticed Retool didn't save my progress as expected twice in the last 24 hours. Seems like they are doing something on their side.
Hello @kleiton_lemos and @Deyan_Totev, my apologies for any issues with saving your apps!
I can check to see if we were having any type of down time with our servers or any events that might have taken place that could have caused this 
Were either of you able to view the save requests in your browsers inspector under the network tab?
Let me know if either of you two are still having ongoing issues with the apps failing to save.
If either of you are still having issues and on the Retool cloud, I can look at your orgs and see if the save requests are making it to our servers, if there are any further details from the logs to pinpoint the issue or if the save requests were not reaching us and getting lost in transmission!
from my side, nothing important was lost; I just wanted to let you know that this thing sometimes happens.
Ok great to hear 
Thank you for letting us know.
We will keep pushing to improve the product and ensure that auto-save continues to function as expected 
Just so you know, this might be part of the kind of issue most users face (with pain), but rarely give feedback on because it usually (magically) get solved 30min to 1 hour after happening...
We lose about 3 to 5 hours every week in our app developments because of this bug.
A fix on these queries edits infinite loading loops would be greatly appreciated 
Hello,
I've been unable to save my requests for an hour now because of the same bug. My organization uses Self-Hosted Retool, so I contacted my administrator, and all our indicators are OK on our infra.
This is a recurring problem that greatly reduces my development productivity. I remain at your disposal for any additional contextual information that may help solve this problem.
AJ
Thank you for sharing this @Laurin_Boujon1!
Apologies for the inconvenience I wish nothing more than for Retool to work consistently and reliably.
Is your org self hosted or on the cloud? If you are on cloud we can look to have some engineers check the logs on your app at given date/time ranges when these query saving bugs were occurring to see if we can find out more about how to fix this.
When the issues are intermittent and hard to reproduce it is very tricky as we have to check the timeline of events to see which of many variables could be contributing/causing this.
But we will be looking to get to the bottom of this and to solve this query edits infinite loading loops bug!
Apologies for this issue.
We will hopefully be able to fix this bug and release and updated version with the fix so that self hosted users like yourself won't have this problem.
We are on self-hosted too, unfortunately
Thank's for your quick answer by the way - we really hope a fix could be pushed soon 
!
1 Like
Hello,
I'm coming back to you because I've been encountering new bugs of the same kind since this morning.
- The reappearance of some transformers I deleted several days ago (I don't know how long ago they reappeared, I just noticed it today).
- The preloaded-js saves itself and works as long as I'm still on the application, but changes are sometimes not saved, except that here I don't have an infinite save to warn me that it's not going to work.
Best regards,
AJ
1 Like
Hello @aj.sopht,
Apologies for this issue. Thank you for reporting these in.
For the reappearing transformers, just want to make sure that you aren't editing or working on the app on multiple tabs at once. As apps can sometimes sync backwards to older versions, if the older version of the app sends in a save request from a browser that is running.
The saving not working is frustrating and I will be adding your +1 to the bug report ticket i filed for our engineers to work on.
Hi @Jack_T,
We've checked deeper into the HTTP requests to better unsderstand the issue.
It seems that we get a 413 Payload too large issue.
While checking the payload, we were absolutely shocked by its size 
(at least 1.6 Mo, according to Header lentgh).
It seems that after each query saving, the whole app is passed to save the changes.
Still, we hardly understand why that is not a repeatable bug - sometimes it works, sometimes the payload gets too big.
I'd like to draw your attention to the fact that we can no longer modify our application, which is used daily by dozens of large customers, and that Retool support is not giving us any answers.
Could we get in touch with your technical teams as soon as possible?
Hello @Laurin_Boujon1,
Apologies for the issues. That is very concerning that you can't modify the application.
Let me see if our engineers are able to see if there are any issues with we can identify on our end with your org/application.
Is your org "sopht1.retool.com"? By 1.6 Mo, did you mean to say 1.6 Megabytes?
Thank you for sharing the screenshot and that your browser is getting a 413 Payload too large response from the servers. That payload size is much larger than I would expect. That is frustrating that there isn't an obvious cause for when that does happen and why at other times it works correctly 
Let me check with our internal team and see if anyone else has encountered this issue before, I can't seem to replicate it with any of my apps
Hi @Laurin_Boujon1,
I just checked with our team. A 413 error typically means the reverse proxy/load balancer in front of their Retool instance is blocking it for that reason.
Were you able to see a x-request-id header on the 413'ing response? If there isn't a x-request-id being returned then then we can confirm the request is not reaching the retool server.
If you are using nginx or our https-portal image (which is nginx under the hood), you would need to set the client_max_body_size to a higher value. Which would be in your deployments config setup.
This will allow the large requests to pass through to the server. This would be the quickest way to fix this issue, while we continue to triage what is causing a query save to try to save the entire app when there have not been other changes made to the app.
Could you give me more details or possibly screen shots of the current state of the app if it is still not modifiable? Is the app not responding to clicks or not loading upon logging in the your org and selecting the app to edit?
Hi @Jack_T !
Sorry for late response ; we investigated the issue and found out that this was linked to our reverse Proxy.
In this case, you can note that an increase of the max body size in the ingress annotation should be done to solve the issue.
Hope it might help some other folks
Best,
1 Like
@Laurin_Boujon1 That is so great to hear!
Thank you for sharing your solution.
Hopefully it can help other users that run into the same issue.