I just fixed my application by redeploying my backend and restarting all services including the db.

This was related to an incident at https://status.railway.com/cmli5y9xt056zsdts5ngslbmp. Apologies for the inconvenience, and glad you got it sorted out!