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
We have received reports from a customer that some requests the CLI makes are failing with 502 errors, causing the CLI to fail with non-zero exit status, despite having set a very high max retry count. However, Sentry CLI does not retry requests to the API that was failing (in this case, the GET /organizations/{}/chunk-upload/ endpoint).
We should investigate whether we can just add consistent retry logic to all of the requests that Sentry CLI makes. If this is feasible, we should just retry all requests; if it turns out that retrying all requests is not desirable, we should at least retry the chunk-upload endpoint, since we know it is blocking a customer.
The text was updated successfully, but these errors were encountered:
We have received reports from a customer that some requests the CLI makes are failing with
502
errors, causing the CLI to fail with non-zero exit status, despite having set a very high max retry count.However, Sentry CLI does not retry requests to the API that was failing (in this case, the
GET /organizations/{}/chunk-upload/
endpoint).We should investigate whether we can just add consistent retry logic to all of the requests that Sentry CLI makes. If this is feasible, we should just retry all requests; if it turns out that retrying all requests is not desirable, we should at least retry the chunk-upload endpoint, since we know it is blocking a customer.
The text was updated successfully, but these errors were encountered: