The SDK guideline has a couple of new items regarding offline caching: getsentry/develop#509

1. If rate-limit was hit, make sure the caching transport is aware. Meaning: don't read all files from disk to send to the HTTP transport when that's basically dropping everything due to rate-limit
2. Add a delay when reading from disk to avoid bursts of events which could trigger rate limit
3. Once the device is back online, read events preciously cached (as opposed to send only on restart or when a new event is captured)

Relates to:

• Offline caching improvements - Delay between and backoff when 429 is on sentry-dotnet#1504
• Offline caching improvements - Delay between and backoff when 429 is on sentry-cocoa#1671