During a regular production deployment for a new version (2.19.0) of Create, clients still referencing the older version (2.18.0) were receiving a 500 error, as it was not included in the release. This was due to an oversight in what clients were still assigned to the older version. Because of the failed requests and subsequent fewer successful calls to the backend services, backend scaling operations scaled down. Once the issue was realized and the release was rolled back, the backend services needed time to scale back up to operational levels. Until that time, many requests continued to receive 500 errors. Once the backend services and databases recovered and scaled to necessary levels, all requests completed successfully.