Recently we received a few requests for handling offline errors, and today we’re announcing that this feature has landed in RootCause.
You can now setup RootCause to capture javascript errors that happen while the browser is disconnected. Most applications don’t have to function in offline mode. Other applications are built specifically for environments that have sporadic or no network (mine workers, oil platforms or other remote areas). For these cases we have introduced a new flag supportOffline : true. Here’s a sample of setting up your RootCause script with this support enabled:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
var logger = new RC.Logger({ applicationId : '6699fc2680f2601917ba69358414fa51', supportOffline : true, checkOnlineInterval : 10 * 1000, recordUserActions : true, recordSessionVideo : true, logAjaxRequests : true, captureScreenshot : true, user : { name : 'Booty Mc Bootstrap', email : 'demouser@therootcause.io', imgUrl : 'https://s.gravatar.com/avatar/0b9e04aed9dcc2d3a121522147dfc7fa?s=80' } }); |
When enabled, video sessions and errors are captured and stored in LocalStorage and if the session cannot be logged, RootCause will retry whenever the network is available again. A neat thing is that the user can reload the page, and our client will retry sending the error until it succeeds (for at most a week).
Try the offline mode support
This feature is available to all our paid plans. Feel free to try this feature in our new Offline Demo. After loading the page, use any method to go offline – turn off your wifi or choose the ‘Offline Mode’ in Chrome Developer Tools. When you are online again – the error will be sent to our server and appear in https://app.therootcause.io/?demo#sandbox-inc/extjs within a minute.
We hope you’ll like the offline support and please let us know if you have any other nice ideas of future features.
Leave a Reply