This feature request is for Store & Forward capability
### Description [**REQUIRED**]
Currently Store and Forward retry is only triggered on a time interval. When many events are being processed and stored for retry, the service can be overloaded by the multiple retries when connection is still lost. A long retry interval avoids this to some degree, but then data is not exported in a timely manner once the connection is restored. It would be more efficient to do the retry when we detect the connection has been restored. Since the use case is many events being processed, we can detect the connection restored by a normal successful export.
### Describe the solution you'd like
Trigger Store and Forward retry when successful export (send) occurs, Store and forward is enabled and a the previous export failed. This enhancement will occur no matter what the retry interval is set to.
### Describe alternatives you've considered
Have you considered any alternative solutions or workarounds?
🚀 Feature Request
Relevant Package [REQUIRED]
This feature request is for Store & Forward capability ### Description [**REQUIRED**] Currently Store and Forward retry is only triggered on a time interval. When many events are being processed and stored for retry, the service can be overloaded by the multiple retries when connection is still lost. A long retry interval avoids this to some degree, but then data is not exported in a timely manner once the connection is restored. It would be more efficient to do the retry when we detect the connection has been restored. Since the use case is many events being processed, we can detect the connection restored by a normal successful export. ### Describe the solution you'd like Trigger Store and Forward retry when successful export (send) occurs, Store and forward is enabled and a the previous export failed. This enhancement will occur no matter what the retry interval is set to. ### Describe alternatives you've considered Have you considered any alternative solutions or workarounds?