My team and I are experiencing two ongoing issues with Retool that we are unable to resolve on our own:
We are constantly losing work. This happens even when we:
Do not have Retool open in more than one tab or browser
Are not working on the same app at the same time as someone else
Save after every change
Have tried in Chrome, Firefox, and Edge
It's not a great experience to have to "export to json" after every single change we make because we live in constant fear of losing over 2+ hours of work (again).
Retool has begun to randomly "glitch" when editing an app. It seems to happen especially when going to edit any component. Here is an example: https://drive.google.com/file/d/1Vd5ZYIjrak40Lv7y-P33tAyoLsI8nDI1/view?usp=sharing. This happens even after reloading the app, closing/reopening app, closing/reopening browser, and across browsers.
Any help in resolving these issues would be GREATLY appreciated! We are building out apps for nonprofits who are greatly in need right now, and if we can't resolve these issues soon we will have to start from scratch on another platform (not ideal).
Apologies for the issue. It sounds like you are following best practices for reducing the risk of any known issues affecting your app building, so this sounds like a deeper issue with your org that we would need to investigate.
Are you self-hosted or on the cloud? If you are on the cloud and share your org name with me, we can check your app logs and see if there is any information on our end that we can find about why the app is not saving correctly.
For your issue 2, I just watched the video, that is very odd and I have never seen that before. My first guess is that the component nesting is trying to figure out the correct size as it seems to be unsure if it should shirk the content and add a scroll bar or make the context slightly larger and remove the horizontal scroll bar.
I would need to do some more testing to confirm, so any steps to reproduce that would be helpful. I would imagine that if you shrink the child component that may get it to fit, it seems to be stuck right around the pixel count that would change the overflow space setting. If you have added any configurations to the 'Appearance' of the component, we could try fiddling with those settings to see if we can get it to not jump between sizing options.
