Back to Catalog
Integration
System Management
Channel Purger
Clear a channel of all messages — for testing, maintenance, or incident recovery.
Intent & Description
Real-world Use Case
Post-incident recovery — a deployment bug published 100,000 malformed messages to a processing queue. Consumers are crashing on every message. Channel Purger is invoked to clear the queue, saving message copies to an audit store. Consumers resume processing clean messages after the fix is deployed.
Source
📌 TL;DR
Channel Purger = nuclear option for queue cleanup. Clears all messages fast. Essential for test resets and poison message recovery. Access-control it tightly and always save copies before purging production.
Advantages
- Fast resolution for poison message incidents that block processing
- Essential for test environment reset between test runs
- Controlled — explicit operation with a confirmation count
- Pair with Message Store to preserve purged messages for analysis
Disadvantages
- Irreversible if messages are not backed up first — data loss risk
- Must be access-controlled — unauthorized purge of production is catastrophic
- Purging a live production channel mid-flow can cause data inconsistency
- Does not fix the root cause — just clears the symptom