When a message fails during processing, 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. A message can have one of the statuses below.
Successful processed message: A message that was successfully processed. Requires message auditing to be enabled.
Message failed one time: A message that was moved to the error queue only one time.
Message failed multiple times: A message that has been retried at least once using tools like ServiceInsight or ServicePulse, and for which retries weren't able to process the message successfully.
Retry requested for message: A failed message, for which a retry was requested from ServiceInsight or ServicePulse. If a message remains with this status, there is no further information about that message, neither failure nor audit for a successful processing. Once the message is re-processed, the status will change to resolved successfully, failed once, or failed multiple times.
Resolved successfully: The message was successfully processed after failure(s).
If the status icon has an exclamation sign overlay (⚠) is shown when the calculated critical time is negative usually caused by clock drift. Clock drift can be migitated by frequently syncing against the same shared time source via NTP.
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, the failed message can be retried from ServiceInsight. Find the message to be retried and click