# Invalid Message Channel

> Malformed messages get their own lane — do not block the main flow with bad data.

- **Category**: Integration
- **Subcategory**: Message Channels
- **Canonical URL**: https://designpattern.fyi/patterns/invalid_message_channel/

---

## Description
Clean, reusable architecture pattern.


## Use Cases
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.





## Trade-offs


### 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




### Considerations & Drawbacks

- 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







---
**Reference**: [Original Source](https://www.enterpriseintegrationpatterns.com/patterns/messaging/InvalidMessageChannel.html)