dead-letter-handling

Route unrecoverable processing errors to a dedicated dead-letter queue.

Updated Mar 29, 2026

Search Tags:#message-queue #error-handling #retries #dead-letter #dlq #poison-message

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill dead-letter-handling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dead-letter-handling
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/dead-letter-handling
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill dead-letter-handling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DLQ handling provides a safe mechanism to capture and manage failed events without dropping data, enabling root-cause analysis and systemic fixes.

Core Features & Use Cases

Dead-letter routing for permanent failures to prevent data loss.
Admin tooling to inspect, requeue, or discard DLQ items and set thresholds.
End-to-end workflow with a durable DLQ table, backoff retries, and monitoring.

Quick Start

Enable DLQ routing in your worker and requeue a test item from the admin dashboard to validate the flow.

Frequently Asked Questions about dead-letter-handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I handle poison messages in a SaaS message queue without dropping data?▼

Poison messages are routed to a dedicated dead-letter queue to preserve data. This approach captures unrecoverable processing errors safely, preventing data loss while enabling root-cause analysis and systemic fixes.

What is the best way to implement retry with backoff for failed webhook deliveries?▼

Retry with backoff is implemented as part of an end-to-end workflow for failed webhook deliveries. It applies progressive retry delays before permanently routing unrecoverable events to a durable DLQ table for investigation.

How do I inspect and requeue failed jobs from a dead-letter queue?▼

You can inspect, requeue, or discard failed jobs using provided admin tooling. These safe admin endpoints allow operators to manage DLQ items directly and set thresholds for automated routing.

When do I need a dead-letter queue for event processing?▼

You need a dead-letter queue when handling permanent failures in event processing. It prevents data loss by capturing unrecoverable errors, allowing you to safely investigate and apply systemic fixes.

Does dead-letter handling work for events, jobs, and webhook deliveries simultaneously?▼

Dead-letter handling applies across events, jobs, and webhook deliveries in SaaS systems. It provides a unified, production-grade pattern to safely manage routing and investigation for all these processes.