In our organization we run a self hosted Retool instance in version 3.75.0.
We are experiencing a bug, where the edit app/module mode gets stuck in a loading screen when a certain number of apps/modules have been opened in edit mode on a certain branch.
Steps to reproduce:
Create a new branch X
Open an app/module, press edit app/module and select branch X.
Wait for it to finish loading.
When clicking on the branch in the bottom, you should see 1 app/module in the list of apps/modules for the branch.
Repeat step 2 until the list shows 4 open apps/modules.
Open a 5th app/module, press edit app/module and select branch X.
The editor will be stuck on the loading screen as this is the fifth app.
The loading screen shows the message "Loading page on branch..." like this:
An admin in our organization found, that when opening the edit mode, that gets stuck, the retool pod, that tries to open the editor, crashes after multiple times logging errors like "Health check error Database connection timed out":
Hey @Walli - Thanks for flagging! I was able to reproduce this on 3.75, and turns out to be a database transaction issue leading to the server hanging until they all time out. We're testing a fix now, but you can try upping the POSTGRES_POOL_SIZE_MAX environment variable from the default of 5 to unblock you in the meantime (would need to be about 1 per number of apps/modules on the development branch to work around for now).
Hi @jmann , thank you for answering and sorry for the late reply due to vacation. I had already solved the issue on our end by a workaround of merging the changes in different branches over multiple steps, so there is currently no blocker for us. But it is good to know, that a fix is being worked on as it might happen again for us in the future. Just fyi, currently, we are on 3.88.0 and the issue seems to still persist.
Hey @Walli - Yup we did backport the fix to 3.75-stable, but we don't do that for edge versions with our release process. It's just fixed on whatever next week's edge release is at the time we fix it, which would be 3.90-edge in this case!
