From 329e9ef7cb08605d690c5e2b962c0c16493c3773 Mon Sep 17 00:00:00 2001 From: Rosa Gutierrez Date: Tue, 23 Dec 2025 20:22:22 +0100 Subject: [PATCH] Don't run application recurring jobs in betas Betas use the same application DB as production, so all these tasks already take place there. Moreover, since betas have different Solid Queue instances, we can't prevent simultaneous runs of the same recurring jobs because each Solid Queue instance is isolated from the others, so they don't know these jobs are running already, leading to all sort of issues. --- config/recurring.yml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/config/recurring.yml b/config/recurring.yml index f59f97ead..6485278b3 100644 --- a/config/recurring.yml +++ b/config/recurring.yml @@ -38,6 +38,14 @@ production: &production schedule: every 60 seconds <% end %> -beta: *production +beta: + # Only Solid Queue maintenance + clear_solid_queue_finished_jobs: + command: "SolidQueue::Job.clear_finished_in_batches(sleep_between_batches: 0.3)" + schedule: every hour at minute 12 + clear_solid_queue_recurring_executions: + command: "SolidQueue::RecurringExecution.clear_in_batches" + schedule: every hour at minute 52 + staging: *production development: *production