Between 15:55 and 17:19 UTC on November 11, some new deployments failed with the error
"Secrets do not exist". This affected deployments that reference a secret whose name contains uppercase letters, even though the secret exists.
We identified the cause as a recent change to how secret references are validated, and rolled it back at 17:19 UTC. New deployments are now working normally.
Services that were already running were not interrupted. If one of your deployments failed with "Secrets do not exist" during this window, please redeploy the service. No changes to your secrets or configuration are needed.
