---
title: Webhook DLQ
description: The dead-letter queue at
---

# Webhook DLQ



## Purpose

WEBHOOK DLQ surfaces incident-webhook deliveries that failed to reach a tenant's endpoint, so a broken integration is loud and actionable. It is an admin view (the panel carries an ADMIN ONLY badge).

Deep link: `ops.useargus.co/#/dlq` (nav group DATA & ADMIN).

## What it shows

FAILED DELIVERIES: both pending rows (still scheduled to retry) and abandoned rows (hit max attempts and parked), up to 200 of each. Columns:

* id (truncated) and idempotency key (truncated)
* target: the webhook URL that failed
* attempts: delivery attempts so far
* last status: the last HTTP status code received
* next retry: when the next automatic attempt is scheduled
* error: the last error message
* action: a RETRY button

Data source: `GET /webhook/dlq?status=pending` plus `GET /webhook/dlq?status=abandoned`.

## Actions

* RETRY re-arms the row (`POST /webhook/dlq/:id/retry`). For an abandoned row this un-abandons it so it is eligible for delivery again. On success the row is removed in place and a toast confirms ("Retry queued for ..."); no step-up confirmation is required.

## Matching CLI

```bash
argusctl dlq ls --status pending
argusctl dlq retry <id>
```

See [argusctl dlq](/docs/cli/dlq).

## Notes

* Polled on the 15 second timer with in-place repaint.
* Empty state: "DLQ is clean".
* Retrying re-arms the row; the actual re-delivery happens only when the DLQ drainer worker runs (per the argusctl reference).


---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)