We sometimes see internal server errors. Would a try/catch catch these database errors allowing us to follow a Plan B workflow?
At the moment I don't understand the root cause of these, or why they exclusively happen at :00 or :30 times. But if we can catch the errors and react properly it will drastically improve the whole process!
The database error itself is. Given up with Xano tech support trying to get to the bottom of this.
"SQLSTATE[08006] [7] connection to server at "database" (10.0.x.x), port 5432 failed: FATAL: sorry, too many clients already connection to server at "database" (10.0.xx.xx), port 5432 failed: FATAL: sorry, too many clients already"
