Retry failed requests
Since publishing this blog post the Retry failed requests feature has been removed.
We hope that you are utilising elmah.io to help you fix your bugs. Deciding if a bug is fixed or not, can be somewhat tricky. To help you investigate, we have launched a new Retry Request feature.
The Retry Request feature is available when expanding an error:
When clicking the icon, the Retry Request dialog is opened:
The dialog is filled with the details from the original and failing request like the URL, cookies, form values, and more. When clicking the Send button, elmah.io retries the failing request and shows the result in the Response section:
In the example above, the failing endpoint has actually been fixed and now returns the status code
200 along with some JSON. If you are using the built-in issue tracker on elmah.io, you can mark this error as fixed once the retry is a success.
We don't want to build a full REST client inside elmah.io (so many good ones already exists), why we allow you to download the complete request as a cURL command. You can either execute it from the command line or import the file into Postman.
Be aware that retrying
DELETErequests (and in some systems GET, oh my!) may make changes in your system.
The retry request feature is currently in beta, and we already have ideas to extend it. As always, let us know if you have input.
We monitor your websites
We monitor your websites for crashes and availability. This helps you get an overview of the quality of your applications and to spot trends in your releases.
We notify you
We notify you when errors starts happening using Slack, Microsoft Teams, mail or other forms of communication to help you react to errors before your users do.
We help you fix bugs
We help you fix bugs quickly by combining error diagnostic information with innovative quick fixes and answers from Stack Overflow and social media.