riverqueue / riverqueue/river

Sequences and batching

Open
#1,128 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

pro
Dominant language
Go
Stars
5.7k
Forks
179
Avg merge
15h 43m
Merged PRs (30d)
13

Description

I have a job that I would like to batch, but also be part of a sequence. In the docs it says these two features should work together. However, when I have my job sequenced and batched by the same field level argument, I've noticed that the sequence takes precedence and doesn't allow the jobs to be batched together. (One job gets worked on at a time).

How should these components work together? Could I have something misconfigured?

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No files, tests, or entry points are named. Reproduce a job configured with sequencing and batching on the same field-level argument, then compare the observed one-at-a-time processing with the documented behavior; done means clarifying whether the interaction is supported, identifying any required configuration, and updating the relevant documentation or behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.