You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When GitLab starts up, the API isn't immediately available, even though the service has started. If label caching is enabled, API connection failures should result in an exponential backoff sequence capped at some amount after which the service should simply fail.
Optionally, status information about the backoff should be posted to the default channel for the Slack webhook so that there's some notification of this happening.
The text was updated successfully, but these errors were encountered:
When GitLab starts up, the API isn't immediately available, even though the service has started. If label caching is enabled, API connection failures should result in an exponential backoff sequence capped at some amount after which the service should simply fail.
Optionally, status information about the backoff should be posted to the default channel for the Slack webhook so that there's some notification of this happening.
The text was updated successfully, but these errors were encountered: