If Raygun4Net can not send the report, then it will cache the report in isolated storage, as long as that's available. Raygun4Net will not listen to when a connection is restored, but instead will re-attempt sending cached reports the next time that a new report succeeds to be sent, or when the application starts up again.
Our clients are long running processes, potentially not restarting for very long times if the machine keeps running or the user Hibernates between sessions. We don't expect many errors, and if the error is only re-sent when the app starts or another error occurs we may not get it for weeks...
Our clients do detect restored connection and could send offline reports (if any) when coming back online
From https://raygun.com/forums/thread/102887
Our clients are long running processes, potentially not restarting for very long times if the machine keeps running or the user Hibernates between sessions. We don't expect many errors, and if the error is only re-sent when the app starts or another error occurs we may not get it for weeks...
Our clients do detect restored connection and could send offline reports (if any) when coming back online