Issue Description
Hello, I am seeing some instances where we encounter error logs like this:
sentry -- exception happened in background worker: Failed to open TCP connection to o4504402941313024.ingest.sentry.io:443 (execution expired)
These are sporadic (at most 3 a day), and there are other messages sent successfully to sentry around the same time. Presumably these are just some connection blip, but I wanted to understand whether these failures would be retried by the sentry worker, or if it could mean messages are getting dropped and never reported to sentry?
Reproduction Steps
Can't reproduce this consistently
Expected Behavior
Any connection failures to *.ingest.sentry.io would retry
Actual Behavior
Connection failures are getting logged
Ruby Version
3.3.6
SDK Version
5.22.3
Integration and Its Version
No response
Sentry Config
No response
Issue Description
Hello, I am seeing some instances where we encounter error logs like this:
These are sporadic (at most 3 a day), and there are other messages sent successfully to sentry around the same time. Presumably these are just some connection blip, but I wanted to understand whether these failures would be retried by the sentry worker, or if it could mean messages are getting dropped and never reported to sentry?
Reproduction Steps
Can't reproduce this consistently
Expected Behavior
Any connection failures to
*.ingest.sentry.iowould retryActual Behavior
Connection failures are getting logged
Ruby Version
3.3.6
SDK Version
5.22.3
Integration and Its Version
No response
Sentry Config
No response