---
title: "Discussion on \"How to send a reminder 24 hours after signup without a queue\" | Hashnode"
description: "Discussion on \"How to send a reminder 24 hours after signup without a queue\". \"Send a reminder email 24 hours after someone signs up\" sounds simple until you try to build it. You can't sleep for a day inside a web request, and a server restart forgets everything in memory. Here"
url: "https://hashnode.com/posts/how-to-send-a-reminder-24-hours-after-signup-without-a-queue/6ae672c8798bf23a40ce4f00"
---

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

Discussion

# [How to send a reminder 24 hours after signup without a queue](https://delayrun.hashnode.dev/how-to-send-a-reminder-24-hours-after-signup-without-a-queue?utm_source=hashnode&utm_medium=feed)

"Send a reminder email 24 hours after someone signs up" sounds simple until you try to build it. You can't sleep for a day inside a web request, and a server restart forgets everything in memory. Here

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

-   [#backend](https://hashnode.com/tag/backend)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#architecture](https://hashnode.com/tag/architecture)
-   [#node](https://hashnode.com/tag/node)

## 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 1

Markdown supported · ⌘↵ to post

[Node Edge Ops](https://hashnode.com/@nodeedgeops)

[Nov 10](https://hashnode.com/posts/how-to-send-a-reminder-24-hours-after-signup-without-a-queue/6ae672c8798bf23a40ce4f00/comment/6af265f423eb62f440987746)

Delayed reminders without a dedicated queue only stay correct when the wake source, the idempotency key, and the catch-up path agree. Prefer storing the due timestamp with a stable reminder id, wake from a periodic sweeper or datastore TTL that cannot double-fire the same id, and bound how far catch-up may replay after a process gap so a restart cannot spam every overdue user at once. Keep the send path separate from the schedule write so a transient provider blip does not lose the due row.

Ops prove-out after wiring the sweeper: insert a synthetic reminder due in the near future and confirm exactly one send, then kill the process before due and restart to confirm the same id still fires once. Under a burst of overdue rows, watch send rate and duplicate-id count for one deploy window — if duplicates climb while the sweeper interval stays flat, the claim lock is missing or too short. Keep a canary that still uses the prior schedule store beside the new path so you can tell a sweeper bug from a real provider outage.
