Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Sometimes, when a new version of a Cloud Functions instance is deployed, multiple errors 500 (The request was aborted because there was no available instance) appear before the deployment finishes, triggering log-based alerts. Even so, the instance is successfully deployed, causing confusion.
What you expected to happen:
These Health Check errors should not be visible as it creates noise in the logs and causes confusion on the customer side
Other information:
These errors do not affect the performance on the customers side.