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
The exact steps vary from user to user. Here is the resume:
Try to upload a large quantity of debug files or source maps to Sentry (can be large files or many files)
The upload command will fail with a 504 gateway timeout.
Setting the region-specific URL (de/us.sentry.io) does not has an effect on the result.
Expected Result
All files are uploaded without error or having to batch uploads manually.
Actual Result
Sentry CLI (or a plugin that uses it) receives a 504 response from Sentry:
error: API request failed
2024-12-19T07:41:30.6452259Z caused by: sentry reported an error: gateway timeout (http status: 504)
As an initial solution, SRE team increased timeouts in Sentry (internal ticket link). Although this solved the issue for some users, there are still users getting 504 timeouts during file upload.
The issue linked above has the logs for affected users (including organisation slugs).
Product Area
Processing
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered:
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
The exact steps vary from user to user. Here is the resume:
Setting the region-specific URL (de/us.sentry.io) does not has an effect on the result.
Expected Result
All files are uploaded without error or having to batch uploads manually.
Actual Result
Sentry CLI (or a plugin that uses it) receives a 504 response from Sentry:
As an initial solution, SRE team increased timeouts in Sentry (internal ticket link). Although this solved the issue for some users, there are still users getting 504 timeouts during file upload.
The issue linked above has the logs for affected users (including organisation slugs).
Product Area
Processing
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: