All four of your services currently show SUCCESS deployment status with no infrastructure-level failures detected. The shift from 502 to 400 errors indicates your application is now running and responding, but the requests are being rejected at the application level rather than timing out at the gateway. Are you still seeing the errors?

Yes,i'm still seeing the errors.

Which is strange because there were no code changes and application changes at all....so how did the application go from working perfectly fine to then throwing errors.

Can you share some of the logs that are showing the 400 errors so we can investigate further?

See attached the log files...The architecture is a front end angular with express and a directus headless cms as the backend connecting to postgres.The current code on prod has been retested on local and it doesn't throw any errors.

Sorted this out.....The issue was the database,had to isolate because i knew there were no code changes to throw app level errors all of a sudden.

i'm guessing the database rolled back to the initial deployment after the outage,but directus has been applying schema changes.So the app was throwing 400 errors when these changes weren't seen in the DB