After migrations (dbmate up): relation 'table_name' does not exist (postgres)

[creimers]

I'm using dbmate with a postgres database hosted on digital ocean, and I'm observing a very odd behavior.

In my production deployment github action, I use dbmate to update the database schema by running dbmate up.

• subsequently, for a short amount of time, the database will throw an error: "relation 'table name' does not exist".
• this error is being thrown even though the migrations are applied smoothly and the relations do as a matter of fact exist.
• while this error persists, the webapp connected to the database does not work properly. Any interaction that requires database access does not work.
• the database is also connected to a retool admin app.
• reloading any retool page TWICE will make the problem go away. On the first load, the 'relation does not exist' error is being displayed. On the second load, this error vanishes and all data is loaded as expected.
• once this 'relation does not exist' error vanishes, all database interactions run as expected.

While I don't think that this is a bug in dbmate, I was hoping to get some helpful comments from the community here. Thanks!

[creimers]

This is no longer happening. It seems to have been related to some specific nodejs version in the github actions. Still very mysterious, but I will not bother now that things work again as expected.