Blake Gentry

Weeeird. I suspect this may have broken during a transition to Astro and we didn’t catch it. Thanks for reporting, hopefully I can fix it soon!

@mauza can you give any more info about how you’d want to use this? There are sort of two features conflated together here and I’d like to understand which one...

Hi everyone, we added a ["sequences"](https://riverqueue.com/docs/pro/sequences) feature to River Pro in the latest release: https://riverqueue.com/blog/river-pro-sequences This should address the use case here. We're still working on other ways of limiting...

@alexanderenam I'm guessing what happened here is that your leader node changed a little after midnight UTC, and due to `RunOnStart: true` the new leader attempted to insert a periodic...

I don't believe there's a remaining issue here so I'm going to close this one out. If you want to ensure consistent once-daily execution times, you have a few options:...

@jackc Just pushed an updated version, is this roughly what you had in mind? Note that I needed to introduce a mutex for synchronization over the new timer field. I...

@jackc I rebased this and trimmed out the unnecessary diff. The flaky test failure I got appears to be unrelated—at least I can't see a reason why changes would cause...

I'm not sure I understand the situation you're encountering. Insert-only clients are those which do not have `Queues` configured, and [they cannot be started](https://github.com/riverqueue/river/blob/master/client.go#L665-L667). They do not run leadership election,...

@elee1766 Just getting back to this, I still do not understand the issue you're describing here. What is your setup? What do you mean that "the job rescuer loses jobs"?