Hey @ChiEn thank you for the response!
This would be for our company organization on a self-hosted instance.
Ah I see, whats the company org? @AJVancattenburch
Hey @ChiEn I have the same issue, Im using the cloud version, If I deploy my code then it is updating but dev mode is unusable, any suggestions ?
4 Likes
Hey there @Nir_Graziani! Welcome to the Community forum!! 
Just to clarify, when you said dev mode is unusable, do you mean that dev mode is not reflecting your latest changes and you only see updates after deploying the app?
Hey Nir could you be a bit more specific about dev mode being unusable? Does it show up in version select, and when you save custom component code locally, does it make a toast on your retool app says “Updating custom components in dev mode, Components should refresh automatically”?
Thanks!
1 Like
Hey @ChiEn thank you for the quick response, yes this is exactly what I mean 
I also had this issue, and this is my workaround:
Open DevTools, go to the Settings, enable “Disable cache while DevTools is open”, Then refresh the app.
With this, my component changes started showing up reliably. It seems like the dev bundle (components.js) was being cached somewhere, and this forces a fresh fetch without needing to deploy.
Hopefully Retool can use this information to fix the dev mode hot-reload so we don’t have to rely on this workaround.
1 Like
Hey @retoolin, Yes I receive the “Updating custom components in dev mode, Components should refresh automatically” message as usual, and unfortunately it does not visually updating
sometimes it updates and when I save again it goes back to a previous version and kind of switch between version
@Simon_Damiaens Trying this rn
1 Like
@ChiEn @retoolin Thank you for the help
@Simon_Damiaens’s solution works but it requires me to keep the DevTools window open at all time
which is ok for me for the meantime.
Thank you @Simon_Damiaens !
1 Like
Gotcha. Thanks for the hint @Simon_Damiaens we will try to fix this now
1 Like
Disabling the cache in Chrome DevTools only turns off caching on the client side (browser). If you’re using self-hosted Retool and something on the server side is also caching requests, this solution won’t work.
Folks, fix just went out, in latest cloud version it will explicitly not cache for dev revisions. Let us know if it works.
1 Like
@Nir_Graziani @Simon_Damiaens @MChuduk I'm marking @retoolin’s update as the solution for visibility. Please let me know if things are still not working on your end, thank you! 
1 Like
Is there a solution for self-hosted?
Unfortunately Q1 stable release does not have this specific fix, try this edge release or after: Image Layer Details - tryretool/backend:3.342.0-edge
^ (I just missed the reply button🙏) Unfortunately Q1 stable release does not have this specific fix, try this edge release or after: Image Layer Details - tryretool/backend:3.342.0-edge
Just checking if you were able to try the edge release above? @djw