From one moment to the next, all queries to RetoolDB stopped working and time out after loading for quite a while. The Database itself is unavailable from the UI. This is critical, as my organization (ecsomsa.retool.com) is an internal tool I'm developing for a client, and it's currently in production. I need to solve this ASAP!
Sorry, posting again as I don't know how to use the tag system, but I'm sure it's helpful to get this viewed as quickly as possible.
From one moment to the next, all queries to RetoolDB stopped working and time out after loading for quite a while. The Database itself is unavailable from the UI. This is critical, as my organization (ecsomsa.retool.com) is an internal tool I'm developing for a client, and it's currently in production. I need to solve this ASAP!
Hey @Franco_De_Simone - welcome to the community and thanks for reaching out! 
We don't do a very good job of surfacing this particular error, but it looks like you maxed out the allocated number of connections to your RetoolDB instance. We restored functionality by restarting the associated compute resource, but it's possible that this will continue to be an issue going forward.
Connections made to the RetoolDB through in-app resource queries are pooled by default, but direct connections generally aren't. Are you frequently connecting to the database from outside Retool? If you are, it might make sense to do so through a pooler like Sequelize.
That said, many organizations simply outgrow the capabilities of RetoolDB and benefit greatly from switching to a dedicated external solution. We make a note of this in our docs:
I hope this context help! Let us know if you have any additional questions.
1 Like
Thank you for your response! Yes, I was connecting to the Retool DB from a PostgreSQL for dev and debugging purposes, so maybe that was the issue, as I don't believe the queries made from Retool Apps or Workflows could be too much for the database to bear with this particular organizations (I've implemented Retool for other clients, in bigger projects, and this has never happened). It probably has to do with my remote connection from outside Retool. Anyway, we're already migrating our data to an external database, so I'm sure I won't have this problem again. Thank you for your help!
1 Like