Back to Catalog
Integration
Message Channels
Invalid Message Channel
Malformed messages get their own lane — do not block the main flow with bad data.
Intent & Description
Real-world Use Case
Payment processing pipeline — a message arrives with a missing currencyCode field. Instead of crashing or retrying infinitely, it is routed to invalid-payments-channel with context (why it failed, original message, timestamp). Ops team sees it in a monitoring dashboard, corrects the upstream system, and resubmits the fixed message.
Source
📌 TL;DR
Invalid Message Channel = the bad data siding track. Malformed messages get routed aside, not discarded and not blocking. Preserve for inspection, fix and resubmit. Always monitor its depth.
Advantages
- Main processing pipeline stays healthy — bad messages do not block good ones
- Invalid messages are preserved for inspection and remediation (no silent discard)
- Clear operational signal — invalid-message channel is a queue depth metric to alert on
- Enables automated or manual remediation workflows
Disadvantages
- Invalid Message Channel needs its own monitoring and operational process
- If not actioned, messages accumulate and the problem is hidden
- Validation logic must be comprehensive — gaps allow corrupt messages through
- Remediation and resubmission workflow must be built