Repository navigation
Sending captured events should honor sending fail. #932
Description
Description
Sending captured events should honor sending fail.
When does the problem happen
- During build
- During run-time
- When capturing a hard crash
Environment
- OS: Unrelated
- Compiler: Unrelated
- CMake version and config: Unrelated
Steps To Reproduce
- Generate crash under Sentry SDK. That should trigger unsent event inside sentry database folder
- Turn off networking
- Run Sentry SDK again.
Expected: The event is not send and event metadata is not removed, appropriate log statement raised.
Actual: Event is not send, event metadata is removed.
Log output
Activity
supervacuus commentedon Jan 8, 2024
There is currently no transport transactionality of events. If an event ends up in the send queue and the transport cannot send for whatever reason, the event is lost. If your use case expects regular network unavailability and requires delivery guarantees, the transport implementation can be customized.
Send errors should be visible in the logs.
stima commentedon Jan 8, 2024
Thanks I would consider to look to custom transport impelementation.
supervacuus commentedon Jan 10, 2024
Btw since you use
crashpad, implementing a custom transport will not help you with adding delivery guarantees for crashes since thecrashpad_handleruses its own transport.7 remaining items
jpnurmi commentedon May 8, 2026
I believe this has been addressed by the recent HTTP retry and offline-caching -related work:
HTTP retry persists envelopes for retry with exponential backoff on network failures
Offline caching keeps failed envelopes in a persistent cache
Consent-aware offline caching preserves envelopes while consent is revoked and retries them once consent is granted
Please let me know if anything is missing. 🙏