Please replay asap

Our client's are becoming very angry

please I need a quick response. it's a emergency situation for us.

any update

Your services were not permanently removed. Our audit logs show that each time the workspace usage/spending limit was modified, all services across every project were simultaneously torn down and redeployed, causing downtime. This happened multiple times on July 18 (around 04:33, 12:17, 14:20, and 21:46 UTC), each triggered by a usage limit change from your workspace. All 21 services across your 6 projects are currently running, and your database volumes (Postgres, MongoDB, KeyDB, Chroma) retained their data through each redeployment. As an immediate workaround, please avoid modifying the workspace usage/spending limit while your services are running, as each change is currently triggering a full redeployment cycle across every service.

no it's happend without changing spending limit also. I only change spending limit to check if it crash because of spending limit or not. I think issue is form something else. can you get a real human to answer

The redeployments are caused by the workspace usage limit cycle. When usage hits the hard limit, all workloads are taken offline to prevent further charges, and when the limit is raised or removed, all services are automatically redeployed. Each time you adjusted the limit to test, that triggered another full redeployment cycle across every project. Your services were never deleted, and all database volumes retained their data through each cycle. To prevent this from recurring, either raise the hard limit well above your expected usage at your usage page or remove it entirely so the stop-and-restart cycle does not repeat.