---
title: "Discussion on \"Dead letter queues for HTTP jobs: what they are and how to use one\" | Hashnode"
description: "Discussion on \"Dead letter queues for HTTP jobs: what they are and how to use one\". Retries fix most failures. An endpoint was restarting, a database was briefly locked, a third-party API hit a rate limit: try again a few minutes later and it works. But some jobs fail every time, no"
url: "https://hashnode.com/posts/dead-letter-queues-for-http-jobs-what-they-are-and-how-to-use-one/6ae672fa2ffc6226c1a74302"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Dead letter queues for HTTP jobs: what they are and how to use one](https://delayrun.hashnode.dev/dead-letter-queues-for-http-jobs-what-they-are-and-how-to-use-one?utm_source=hashnode&utm_medium=feed)

Retries fix most failures. An endpoint was restarting, a database was briefly locked, a third-party API hit a rate limit: try again a few minutes later and it works. But some jobs fail every time, no

Oct 31 · 4 min read · delayrun.hashnode.dev  
Read the article

-   [#architecture](https://hashnode.com/tag/architecture)
-   [#backend](https://hashnode.com/tag/backend)
-   [#reliability](https://hashnode.com/tag/reliability)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[delay.run](https://hashnode.com/@delayrun)

@delayrun

  
[View profile](https://hashnode.com/@delayrun)

Hosted cron jobs over plain HTTP, with retries, run logs and alerts.

delay.run calls your URL on a cron schedule, after a delay, or right away from one API call. No SDK and no server to maintain. Every run is logged with its request and response, failed jobs are retried with backoff, and alerts go to email, Slack or Discord. Starts with 1,000 free requests. https://delay.run

## Responses

Markdown supported · ⌘↵ to post

No responses yet.