When message processing fails NServiceBus will automatically retry it. If a message continues to fail it will be forwarded to the error queue and become visible within ServiceInsight.
The views in ServiceInsight show information about message processing failure with the message. No manual correlation of log files or accessing of remote servers is necessary to research the reasons for an error.
The status of an errant message is illustrated in the message window.
The flow diagram highlights errors in red and provides details with access to the stack trace.
The sequence diagram highlights handlers with errors in red.
Once the underlying cause for message processing failure has been resolved it is possible to retry a failed message from within ServiceInsight. Find the message to be retried and click