Hi!
We have version 3.28.3 and want the latest.
But this failed, even if I tried to downgrade slowly to different versions along the way.
Does it exist any migration guide or things to think about when upgrading?
The primary error is on the retool DB that fails to read from and write to. Im sorry its a while since I tried as I expected return on a support email, and have lost the logs.
This is an attempt to try to get some pointers on what to do, and what can help? Maybe someone has experienced this before?
Instead of downgrading from the high version, I think you'd better do the opposite:
- Recover to your original verison 3.28.3 with your original backup data, and verify if it's still working
- Gradually upgrade the version, for example from 3.28 -> 3.33 -> 3.52 -> 3.75
Cuz if you data migration to the very latest version failed, you data might have already corrupted.
I did encounter RetoolDB issue few times when I still still in testing deployment trying different versions. But my org doesn't use Retool DB for permernant data storage, so remove the volumn and let the docker recreate one would fix my issue. This might not be your case.
@zelterNN thanks for the thoughts! I forgot to say that downgrading back to 3.28.3 worked fine and I have my setup running again. Hence the forgetting of the error and not screaming of panic 
But I can absolutely try slowly upgrading and see if this helps. Just not nessecarily what I wanted 
Do you have a snapshot of your db? If so, revert to the snapshot and start the process again.
If not, export your apps and import them into a new instance. You can then go back to the original version and try troubleshooting from there.
We generally advise against downgrading Retool versions because the schema remains at the higher Retool version and may become corrupted if you make a big jump in versions.
The primary error appears to be with the Retool DB failing to read from and write to. Did downgrading solve the issue you mentioned?
For best practices, check this guide: Self-hosted Retool upgrade best practices | Retool Docs
So I went with a solid upgrade, the errors started showing. I gradually downgraded and ended up going back to my original version, so yeah downgrading worked.
Meaning that its nothing wrong with the migrations I assume, but something with the setup of reading from the DB?
Our Docs recommend if your current version is more than 10 versions behind, upgrade incrementally (e.g., 3.0, 3.10, 3.20...) and verify each installation. We also encourage if you're upgrading in batches, create a backup before each batch. If you run into any issue send over the logs and I'd be happy to take a look!