Add bridge critical error action#858
Merged
Merged
Conversation
tamararivera
approved these changes
Jun 5, 2026
ngallegos
approved these changes
Jun 5, 2026
andreasohlund
approved these changes
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a public
BridgeConfiguration.DefineCriticalErrorAction(...)API so bridge hosts can configure a response to critical errors using the same delegate shape as regular NServiceBus endpoints.The configured action is stored in the finalized bridge configuration and applied to the raw endpoint configuration for both bridge proxy endpoints and send-only dispatcher endpoints. This keeps the action wired through transport
HostSettings.CriticalErrorAction, matching the convention used by NServiceBus Core.Testing
HostSettings.CriticalErrorActionfor both dispatcher and proxy raw endpoints.