Inspect message content, metadata, state or routing configuration.
System Management
Detour
Temporarily divert selected traffic through an additional path and return it to the normal route afterward, without permanently redesigning the flow.
How can you route a message through intermediate steps to perform validation, testing or debugging functions?Adapted from Enterprise Integration Patterns under CC BY 3.0. The visualization and explanatory content on this page are original GateSift material.
Original GateSift visualization
How Detour works
A routing decision sends the message along one of several possible paths.
Incoming message
Detour
Route A
Route B
Fallback
Use Detour to select the next destination or processing step.
Continue on the selected path while keeping the producer decoupled from destinations.
What this pattern helps you decide
Temporarily divert selected traffic through an additional path and return it to the normal route afterward, without permanently redesigning the flow.
What happens when processing fails or the same message is delivered twice?
Where does state, correlation or routing configuration live?
How will operators trace the message and understand the decision path?
Where you may see it
- APIM conditional diagnostic backend
- Feature-flagged Logic App branch
- BizTalk temporary send-port route
How the analyzers can surface it
- Conditional diagnostic branches
- Temporary routing configuration
Pattern detection is contextual. GateSift should present these as architectural signals, not claim a pattern is implemented solely because one policy statement or adapter exists.
Source, licence and attribution
The pattern name and selected problem statement are adapted from Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf under CC BY 3.0. GateSift summaries, Azure mappings, analyzer guidance and diagrams are original. No endorsement by the original authors is implied.