solid_queue
solid_queue copied to clipboard
Database-backed Active Job backend
I'm currently trying to instrument how long a job stays in the queue before it's picked up for processing. From what I can tell, there's a finished_at timestamp available, but...
Hi, first of all, thanks for Solid Queue, we're currently using it in production and really like its simplicity and Rails-native design! One challenge we've run into: when running IO-heavy...
Having only one file to configure recurring tasks is not optimal when handling several engines within the same codebase that are isolated from each other. With these changes, it will...
I'm testing a recurring job in development which works fine but when I comment it out or remove it from recurring.yml and restart the system, it still appears in the...
Seems like it happens when forking. Contents of my puma.rb ```ruby threads_count = ENV.fetch("RAILS_MAX_THREADS", 3) threads threads_count, threads_count # Specifies the `port` that Puma will listen on to receive requests;...
When I start my project from the devcontainer with solid_queue and the puma plugin, I get several `#` related to the debugger: ``` 21:07:26 web.1 | Puma starting in single...
Hey there! We've been using SolidQueue for a while now, and we're really happy with it. But there's one thing that's been bugging us a bit. Sometimes, the workers just...
Sending the confirmation mailer in my Rails app sometimes fails randomly without raising any exception. I discover it only when I visit the dashboard, and I see the following error:...
Hi folks! I've been using Solid Queue in my Rails app and loving it so far. However, I've run into an interesting use case that I'd love to discuss and...
Using retry_on like so: ``` class SyncJob < ApplicationJob include Common queue_as :scheduler retry_on StandardError, wait: 5.seconds, attempts: 3 ``` is scheduling the first run to 5 seconds from now:...