Delay sending and Message.OccurredOn

We have a modified version of the Raygun .NET client that uses a SQLite database to locally persist the error message. When the error message is successfully submitted to the Raygun endpoint we remove the local copy. This reduces the likelihood of missing error reports when the client is disconnected from the internet or crashing hard.

The current app.raygun.io dashboard seems to sort reports using the OccurredOn property. When reports are sent after the actual crash they are lost in the current UI.

As a workaround we set OccurredOn to DateTime.UtcNow at the time of submission and store the actual OccurredOn property in custom user data.

It would be nice if the current model was extended to include a SubmittedOn property. This property could be used by the UI for sorting.

Thanks!

---

Hi Scott,

I would suggest storing the SubmittedOn value in the custom user data and not the OccurredOn value. Currently this will mean that you will have the issue you mention. But we are hoping to have custom filtering, ordering and searching available in the near future which would allow you to order by your custom user data values and keep the 'correctness' of your data.

You can load more errors in the current UI with the button at the end of the list on the main dashboard if you know that an error should be their but has an older OccurredOn value.

Thanks for the feedback

Martin

---