FlowchartRetry & error handlingMedium

Dead-letter queue handling

Consumer with main queue, retry queue, and dead-letter queue for poison messages.

What this diagram shows

Step 01

Main path

Producers push to the main queue and consumers ack the happy path.

Step 02

Retry queue

Transient failures land in a retry queue that feeds back into the consumer.

Step 03

Poison isolation

Messages that keep failing move to a dead-letter queue for manual triage.

About flowchart diagrams

Flowcharts map out a process as boxes and arrows. They work well when you need to explain how a decision, workflow, or pipeline moves from one step to the next.

This template is written in Mermaid — plain text you can edit, version in git, and regenerate the image from any time.

View Mermaid sourcePlain-text diagram syntax — copy or edit directly.

diagram.mmd

1graph LR
2  Producer[Producer] --> Main[(Main queue)]
3  Main --> Consumer[Consumer]
4  Consumer -->|ok| Ack[Ack]
5  Consumer -->|fail| Retry[(Retry queue)]
6  Retry --> Consumer
7  Consumer -->|exceeded retries| DLQ[(Dead-letter queue)]
8  DLQ --> Triage[Manual triage]

Related templates

More templates that cover similar workflows.

FLOWCHART

Slate

Webhook delivery with retry

Outbound webhook pipeline with signing, retry on failure, and dead-letter fallback.

API workflowMedium8 nodes

FLOWCHART

Obsidian

Retry with exponential backoff

Retry strategy using exponential backoff with jitter and a hard cap on attempts.

Retry & error handlingMedium6 nodes

FLOWCHART

Atlas

Microservices overview

High-level view of a microservices system with gateway, services, and shared datastores.

System architectureMedium8 nodes

FLOWCHART

Brutalist

GitHub Actions release pipeline

CI pipeline running lint, test, build, tag, and publish through GitHub Actions jobs.

CI/CD pipelineMedium7 nodes