Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support delayed jobs in PersistedQueue

Open
#8,906 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@tim-smart is already working on this.

Since Oct 8, 2026.

  • #8907 by @tim-smart — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript

Research direction

Start by reviewing the existing PersistedQueue API and linked pull request #8907 to understand the proposed approach. Done means jobs can be enqueued with a delay and are processed only after that delay; check the relevant tests alongside the implementation.

Written by the indexing model from the issue text.

Description

enhancement
What is the problem this feature would solve?

Currently PersistedQueue is a super slick module for replacing usages of stuff like BullMQ etc. There's one common use case that for me makes it tricky to completely migrate - the ability to enqueue a job with a delay. For me personally it's a very common use case when using jobs queue. Making sure stuff runs when users are less active, queuing reminders-like stuff, etc.

What is the feature you are proposing to solve the problem?

Allows using PersistedQueue to process jobs with a delay.

Relevant Twitter thread: https://x.com/maxwellbrown/status/2103511404871594431?s=12

What alternatives have you considered?

I also used Cluster with its DeliveredAt annotation to achieve similar behavior while PersistedQueue wasn't there yet. However, in my experience PersistedQueue offers a little bit more simplicity when it comes to just queueing a job and I'd like to use it for that as well. No need for naming entities, better control over old messages etc.

Dominant language
TypeScript
Stars
16.7k
Forks
808
Avg merge
11h 29m
Merged PRs (30d)
453

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Effect-TS/effect

All issues in Effect-TS/effect

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.