Refresh schedule not working

[jonahgreenthal]

Since I upgraded to 26.3.0, my refresh schedules have not been working. There are a number of other issues and discussions that have this same basic complaint. How can we fix this, or what information can we provide to help troubleshoot?

[ekanshul]

A common way schedules "stop working" with no visible error is the auto-disable path in Query.outdated_queries(): if anything goes wrong while evaluating a query's schedule, Redash silently rewrites it to {"disabled": true} and only logs at info level (see #7780).

Two things worth checking to narrow this down:

1. In the database: SELECT id, schedule FROM queries WHERE schedule IS NOT NULL; — if affected queries show "disabled": true (especially if you never disabled them), you hit that path.
2. In the scheduler/worker logs: lines containing Could not determine if query — the message includes the exception that triggered the disable.

If that's what you're seeing, #7789 makes the scheduler tolerant of partial schedule objects (missing time/day_of_week/until keys, HH:MM:SS times) instead of disabling them. If your schedule column looks intact instead, it's a different problem — the output of the two checks above would help either way.

[jonahgreenthal]

1. I don't think this is the issue:

/opt/redash$ docker compose exec postgres psql -U postgres
psql (9.6.15)
Type "help" for help.

postgres=# SELECT id, schedule FROM queries WHERE schedule IS NOT NULL;
 id  |                                 schedule                                 
-----+--------------------------------------------------------------------------
  95 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  93 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  81 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  39 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
 101 | null
  90 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  37 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  89 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  45 | {"time": "05:15", "until": null, "interval": 86400, "day_of_week": null}
  92 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  85 | {"time": null, "until": null, "interval": 21600, "day_of_week": null}
  40 | {"time": "05:15", "until": null, "interval": 86400, "day_of_week": null}
  88 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  79 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  44 | {"time": "05:15", "until": null, "interval": 86400, "day_of_week": null}
  87 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  46 | {"time": null, "until": null, "interval": 300, "day_of_week": null}
  35 | {"time": "05:15", "until": null, "interval": 86400, "day_of_week": null}
  38 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  43 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  91 | {"time": null, "until": null, "interval": 21600, "day_of_week": null}
  36 | {"time": "05:30", "until": null, "interval": 86400, "day_of_week": null}
  86 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
 100 | {"time": null, "until": null, "interval": 21600, "day_of_week": null}
  80 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
  42 | {"time": "05:15", "until": null, "interval": 86400, "day_of_week": null}
  94 | {"time": null, "until": null, "interval": 21600, "day_of_week": null}
  41 | {"time": null, "until": null, "interval": 43200, "day_of_week": null}
(28 rows)

2. I'm not sure what the proper way to look into this is (I'm not good with Docker), but I ran

/opt/redash$ docker compose logs | grep "Could not determine if query"

and got no results. Is that the right way to look? If not, could you point me at how to look? (I did get a warning WARN[0000] /opt/redash/docker-compose.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion, but I don't think that's relevant.)

[ekanshul]

Thanks, that rules out the auto-disable path: the schedules are intact, and docker compose logs across all services is the right place to look, so no Could not determine line means nothing was disabled.

With the schedule data fine, the question is which stage stops: the scheduler not running the 30-second refresh_queries job, that job not considering the queries outdated, or the queries being enqueued and nothing executing them. Two things that tell these apart without much Docker:

1. System Status in the UI (/admin/status). The "Manager" block shows when queries were last refreshed and the outdated queries count. refresh_queries writes both each time it runs, so:

   • last refresh more than a minute old: the periodic job is not running (scheduler down, or no worker listening on the periodic queue);
   • current, but the count stays 0 across several refreshes: the queries are not being picked as outdated (a paused data source also keeps it at 0);
   • current and above 0, but nothing executes: the jobs are enqueued on scheduled_queries and no worker takes them.

   The RQ Status page (/admin/queries/jobs) lists the workers and the queues each one listens on. Something has to listen on periodic and something on scheduled_queries. In the setup repo's compose that is the worker service (QUEUES: "periodic,emails,default") and scheduled_worker (QUEUES: "scheduled_queries,schemas"); adding a worker for periodic is what resolved Scheduled queries don't work in 25.1.0 #7448.

2. docker compose ps for the list of services and whether scheduler and the workers are up, then

   docker compose logs --since 5m worker scheduled_worker
   

   (with your service names). The periodic worker should log Refreshing queries... / Done refreshing queries: {...} every 30 seconds, and the scheduled worker job=execute_query state=executing_query ... lines when a query runs.

If your docker-compose.yml was carried over from v10 rather than taken from the current setup repo, pasting its services and QUEUES values would help too.

[jonahgreenthal]

My scheduled queries randomly started working again. That's good in one way, but it probably makes troubleshooting this harder, and I don't trust that they'll be reliable. So in case it helps, I'm going to provide the information you asked about:

Screenshots of the system status page:

/opt/redash$ docker compose ps
WARN[0000] /opt/redash/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion 
NAME                        IMAGE                  COMMAND                  SERVICE            CREATED         STATUS      PORTS
redash-adhoc_worker-1       redash/redash:26.3.0   "/app/bin/docker-ent…"   adhoc_worker       3 months ago    Up 4 days   5000/tcp
redash-nginx-1              redash/nginx:latest    "nginx -g 'daemon of…"   nginx              3 months ago    Up 4 days   0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp
redash-postgres-1           postgres:9.6-alpine    "docker-entrypoint.s…"   postgres           13 months ago   Up 4 days   5432/tcp
redash-redis-1              redis:5.0-alpine       "docker-entrypoint.s…"   redis              13 months ago   Up 4 days   6379/tcp
redash-scheduled_worker-1   redash/redash:26.3.0   "/app/bin/docker-ent…"   scheduled_worker   3 months ago    Up 4 days   5000/tcp
redash-scheduler-1          redash/redash:26.3.0   "/app/bin/docker-ent…"   scheduler          3 months ago    Up 4 days   5000/tcp
redash-server-1             redash/redash:26.3.0   "/app/bin/docker-ent…"   server             3 months ago    Up 4 days   0.0.0.0:5000->5000/tcp, :::5000->5000/tcp
redash-worker-1             redash/redash:26.3.0   "/app/bin/docker-ent…"   worker             3 months ago    Up 4 days   5000/tcp

docker-compose.yml (yes, this was carried over from v10)

docker-compose-logs.txt

[ekanshul]

Thanks for all the details. Everything in the screenshots and the log window looks healthy: refresh_queries runs every 30 s on the periodic worker, the outdated queries get enqueued to scheduled_queries and complete, and no queue is backed up.

One thing stands out: all four RQ workers were started on 2026-09-05 around 07:04, and docker compose ps shows every container "Up 4 days", so the whole stack was restarted on Sep 5. If that is when the schedules came back, the likely culprit is the scheduler container (rq-scheduler): it is the only thing that enqueues refresh_queries, so if it stalls, nothing is ever refreshed and nothing logs an error, because no worker ever sees a job. In that state the "Last Refresh" value under Manager on /admin/status stops advancing (it should never be more than a minute or so old), which is the quickest tell.

If it happens again, before restarting everything: note the "Last Refresh" value, grab docker compose logs --tail 200 scheduler worker, and try docker compose restart scheduler on its own. If that alone brings the schedules back, we know where to look.

Unrelated to this, but worth doing at some point: the v10 compose file pins Redis 5 and Postgres 9.6, which are well outside what 26.x is tested against. The current reference is data/compose.yaml in https://github.com/getredash/setup (Redis 7, Postgres 17 via pgautoupgrade); take a Postgres backup before switching the Postgres image, since that image upgrades the data directory in place.

[jonahgreenthal]

Thanks. I'd be glad to try an upgrade, but how do I actually do that?

[ekanshul]

Sure. Your app image is already 26.3.0, so this is only about the compose file and the Redis/Postgres containers around it. The current reference file is data/compose.yaml in getredash/setup; it keeps the same service names, the same /opt/redash/env file and the same /opt/redash/postgres-data volume path as yours, so your data and settings carry over. The one real change is Postgres: the new file uses the pgautoupgrade/pgautoupgrade:17-alpine image, which runs pg_upgrade on the existing 9.6 data directory in place the first time it starts (it supports 9.5+, and alpine-to-alpine avoids collation surprises). That step is one-way, so take a backup first.

cd /opt/redash

# 1. Backup the Redash metadata DB and the env file
docker compose exec postgres pg_dump -U postgres postgres > redash-backup-$(date +%F).sql
cp env env.bak

# 2. Stop everything with the old file and put it aside
docker compose down
mv docker-compose.yml docker-compose.v10.yml

# 3. Fetch the current compose file and pin your version
curl -fsSL https://raw.githubusercontent.com/getredash/setup/master/data/compose.yaml -o compose.yaml
sed -i 's/__TAG__/26.3.0/' compose.yaml

# 4. Start Postgres alone and watch the in-place upgrade finish
docker compose up -d postgres
docker compose logs -f postgres     # wait for "database system is ready to accept connections", then Ctrl-C

# 5. Apply migrations (a no-op since you're already on 26.3.0) and start the rest
docker compose run --rm server manage db upgrade
docker compose up -d
docker compose ps

Notes:

• docker compose now defaults to compose.yaml, so the old -f docker-compose.yml isn't needed, and the version: warning goes away.
• Redis has no persistent data in this setup, so jumping from 5 to 7 needs nothing beyond the restart; anything queued at that moment is lost, so do it at a quiet time.
• Make sure there is roughly as much free disk space as /opt/redash/postgres-data uses before step 4.
• If anything looks wrong after step 4, docker compose down, restore from the dump into a fresh postgres-data directory, and you can go back to the old file.

Once you're on it, the future upgrades are just the steps in the upgrade guide: change the image tag, docker compose stop server scheduler scheduled_worker adhoc_worker worker, manage db upgrade, up -d.

[jonahgreenthal]

I'm going to hold off on the upgrade for now because my scheduled queries stopped working again (on September 11). Here are updated screenshots in case you have any debugging tips. Also, if you think I should go ahead and try upgrading anyway, I'm game.

/opt/redash$ docker compose ps
WARN[0000] /opt/redash/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion 
NAME                        IMAGE                  COMMAND                  SERVICE            CREATED         STATUS      PORTS
redash-adhoc_worker-1       redash/redash:26.3.0   "/app/bin/docker-ent…"   adhoc_worker       3 months ago    Up 2 days   5000/tcp
redash-nginx-1              redash/nginx:latest    "nginx -g 'daemon of…"   nginx              3 months ago    Up 2 days   0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp
redash-postgres-1           postgres:9.6-alpine    "docker-entrypoint.s…"   postgres           13 months ago   Up 2 days   5432/tcp
redash-redis-1              redis:5.0-alpine       "docker-entrypoint.s…"   redis              13 months ago   Up 2 days   6379/tcp
redash-scheduled_worker-1   redash/redash:26.3.0   "/app/bin/docker-ent…"   scheduled_worker   3 months ago    Up 2 days   5000/tcp
redash-scheduler-1          redash/redash:26.3.0   "/app/bin/docker-ent…"   scheduler          3 months ago    Up 2 days   5000/tcp
redash-server-1             redash/redash:26.3.0   "/app/bin/docker-ent…"   server             3 months ago    Up 2 days   0.0.0.0:5000->5000/tcp, :::5000->5000/tcp
redash-worker-1             redash/redash:26.3.0   "/app/bin/docker-ent…"   worker             3 months ago    Up 2 days   5000/tcp

/opt/redash$ docker compose logs --since 5m worker scheduled_worker
WARN[0000] /opt/redash/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion 
scheduled_worker-1  | 2026/09/14 02:37:01 [worker_healthcheck] Received TICK_60 event from supervisor
scheduled_worker-1  | 2026/09/14 02:37:01 [worker_healthcheck] Performing `RQ Worker Healthcheck` check for process name worker-0
scheduled_worker-1  | 2026/09/14 02:37:01 [worker_healthcheck] WorkerHealthcheck: Worker rq:worker:b2fc4eb2185c4296aa21ca634e137cf1 healthcheck: Is busy? False. Seen lately? False (283 seconds ago). Has nothing to do? True (0 jobs in watched queues). ==> Is healthy? True
scheduled_worker-1  | 2026/09/14 02:37:01 [worker_healthcheck] `RQ Worker Healthcheck` check succeeded for process worker-0
scheduled_worker-1  | RESULT 2
scheduled_worker-1  | OKREADY
scheduled_worker-1  | 2026/09/14 02:38:01 [worker_healthcheck] Received TICK_60 event from supervisor
scheduled_worker-1  | 2026/09/14 02:38:01 [worker_healthcheck] Performing `RQ Worker Healthcheck` check for process name worker-0
scheduled_worker-1  | 2026/09/14 02:38:01 [worker_healthcheck] WorkerHealthcheck: Worker rq:worker:b2fc4eb2185c4296aa21ca634e137cf1 healthcheck: Is busy? False. Seen lately? False (343 seconds ago). Has nothing to do? True (0 jobs in watched queues). ==> Is healthy? True
scheduled_worker-1  | RESULT 2
scheduled_worker-1  | OKREADY
scheduled_worker-1  | 2026/09/14 02:38:01 [worker_healthcheck] `RQ Worker Healthcheck` check succeeded for process worker-0
scheduled_worker-1  | 2026/09/14 02:39:01 [worker_healthcheck] Received TICK_60 event from supervisor
scheduled_worker-1  | 2026/09/14 02:39:01 [worker_healthcheck] Performing `RQ Worker Healthcheck` check for process name worker-0
scheduled_worker-1  | RESULT 2
scheduled_worker-1  | OKREADY
scheduled_worker-1  | 2026/09/14 02:39:02 [worker_healthcheck] WorkerHealthcheck: Worker rq:worker:b2fc4eb2185c4296aa21ca634e137cf1 healthcheck: Is busy? False. Seen lately? False (403 seconds ago). Has nothing to do? True (0 jobs in watched queues). ==> Is healthy? True
scheduled_worker-1  | 2026/09/14 02:39:02 [worker_healthcheck] `RQ Worker Healthcheck` check succeeded for process worker-0
scheduled_worker-1  | 2026/09/14 02:40:01 [worker_healthcheck] Received TICK_60 event from supervisor
scheduled_worker-1  | 2026/09/14 02:40:01 [worker_healthcheck] Performing `RQ Worker Healthcheck` check for process name worker-0
scheduled_worker-1  | 2026/09/14 02:40:01 [worker_healthcheck] WorkerHealthcheck: Worker rq:worker:b2fc4eb2185c4296aa21ca634e137cf1 healthcheck: Is busy? False. Seen lately? True (57 seconds ago). Has nothing to do? True (0 jobs in watched queues). ==> Is healthy? True
scheduled_worker-1  | RESULT 2
scheduled_worker-1  | OKREADY
scheduled_worker-1  | 2026/09/14 02:40:01 [worker_healthcheck] `RQ Worker Healthcheck` check succeeded for process worker-0
scheduled_worker-1  | 2026/09/14 02:41:01 [worker_healthcheck] Received TICK_60 event from supervisor
scheduled_worker-1  | 2026/09/14 02:41:01 [worker_healthcheck] Performing `RQ Worker Healthcheck` check for process name worker-0
scheduled_worker-1  | RESULT 2
scheduled_worker-1  | OKREADY
scheduled_worker-1  | 2026/09/14 02:41:01 [worker_healthcheck] WorkerHealthcheck: Worker rq:worker:b2fc4eb2185c4296aa21ca634e137cf1 healthcheck: Is busy? False. Seen lately? False (117 seconds ago). Has nothing to do? True (0 jobs in watched queues). ==> Is healthy? True
scheduled_worker-1  | 2026/09/14 02:41:01 [worker_healthcheck] `RQ Worker Healthcheck` check succeeded for process worker-0
worker-1            | 2026/09/14 02:37:01 [worker_healthcheck] Received TICK_60 event from supervisor
worker-1            | 2026/09/14 02:37:01 [worker_healthcheck] Performing `RQ Worker Healthcheck` check for process name worker-0
worker-1            | RESULT 2
worker-1            | OKREADY
worker-1            | 2026/09/14 02:37:01 [worker_healthcheck] WorkerHealthcheck: Worker rq:worker:885e815eedf14d348db13ff927a7d202 healthcheck: Is busy? False. Seen lately? False (81 seconds ago). Has nothing to do? True (0 jobs in watched queues). ==> Is healthy? True
worker-1            | 2026/09/14 02:37:01 [worker_healthcheck] `RQ Worker Healthcheck` check succeeded for process worker-0
worker-1            | [2026-09-14 02:37:21,572][PID:45][INFO][rq.worker] default: efc739c2-7ef7-4b60-8130-cee69bfdc0b4
worker-1            | [2026-09-14 02:37:21,627][PID:293][INFO][rq.worker] default: Job OK (efc739c2-7ef7-4b60-8130-cee69bfdc0b4)
worker-1            | [2026-09-14 02:37:21,628][PID:293][INFO][rq.worker] Result is kept for 500 seconds
worker-1            | [2026-09-14 02:37:39,837][PID:45][INFO][rq.worker] default: abd318c1-18f2-4a6f-bf6d-545ec93dec6a
worker-1            | [2026-09-14 02:37:39,887][PID:294][INFO][rq.worker] default: Job OK (abd318c1-18f2-4a6f-bf6d-545ec93dec6a)
worker-1            | [2026-09-14 02:37:39,887][PID:294][INFO][rq.worker] Result is kept for 500 seconds
worker-1            | 2026/09/14 02:38:01 [worker_healthcheck] Received TICK_60 event from supervisor
worker-1            | 2026/09/14 02:38:01 [worker_healthcheck] Performing `RQ Worker Healthcheck` check for process name worker-0
worker-1            | 2026/09/14 02:38:01 [worker_healthcheck] WorkerHealthcheck: Worker rq:worker:885e815eedf14d348db13ff927a7d202 healthcheck: Is busy? False. Seen lately? True (22 seconds ago). Has nothing to do? True (0 jobs in watched queues). ==> Is healthy? True
worker-1            | RESULT 2
worker-1            | OKREADY
worker-1            | 2026/09/14 02:38:01 [worker_healthcheck] `RQ Worker Healthcheck` check succeeded for process worker-0
worker-1            | [2026-09-14 02:38:04,880][PID:45][INFO][rq.worker] default: f3ffbc17-2e46-4d93-b2d2-6aff74bd25fd
worker-1            | [2026-09-14 02:38:04,938][PID:295][INFO][rq.worker] default: Job OK (f3ffbc17-2e46-4d93-b2d2-6aff74bd25fd)
worker-1            | [2026-09-14 02:38:04,938][PID:295][INFO][rq.worker] Result is kept for 500 seconds
worker-1            | [2026-09-14 02:38:05,881][PID:45][INFO][rq.worker] default: aee74e91-e156-44b8-9c36-89beee51d6fc
worker-1            | [2026-09-14 02:38:05,929][PID:296][INFO][rq.worker] default: Job OK (aee74e91-e156-44b8-9c36-89beee51d6fc)
worker-1            | [2026-09-14 02:38:05,930][PID:296][INFO][rq.worker] Result is kept for 500 seconds
worker-1            | 2026/09/14 02:39:01 [worker_healthcheck] Received TICK_60 event from supervisor
worker-1            | 2026/09/14 02:39:01 [worker_healthcheck] Performing `RQ Worker Healthcheck` check for process name worker-0
worker-1            | 2026/09/14 02:39:02 [worker_healthcheck] WorkerHealthcheck: Worker rq:worker:885e815eedf14d348db13ff927a7d202 healthcheck: Is busy? False. Seen lately? True (56 seconds ago). Has nothing to do? True (0 jobs in watched queues). ==> Is healthy? True
worker-1            | 2026/09/14 02:39:02 [worker_healthcheck] `RQ Worker Healthcheck` check succeeded for process worker-0
worker-1            | RESULT 2
worker-1            | OKREADY
worker-1            | [2026-09-14 02:39:05,220][PID:45][INFO][rq.worker] default: fab43274-7e75-4d85-b79c-9cf44e2c4fc6
worker-1            | [2026-09-14 02:39:05,268][PID:297][INFO][rq.worker] default: Job OK (fab43274-7e75-4d85-b79c-9cf44e2c4fc6)
worker-1            | [2026-09-14 02:39:05,268][PID:297][INFO][rq.worker] Result is kept for 500 seconds
worker-1            | [2026-09-14 02:39:09,255][PID:45][INFO][rq.worker] default: 7e4168bb-e7fd-43ff-a45d-e96eae515ba4
worker-1            | [2026-09-14 02:39:09,306][PID:298][INFO][rq.worker] default: Job OK (7e4168bb-e7fd-43ff-a45d-e96eae515ba4)
worker-1            | [2026-09-14 02:39:09,307][PID:298][INFO][rq.worker] Result is kept for 500 seconds
worker-1            | [2026-09-14 02:39:10,262][PID:45][INFO][rq.worker] default: d4bc4101-1947-4d99-af4f-f6683cf4fcfd
worker-1            | [2026-09-14 02:39:10,311][PID:299][INFO][rq.worker] default: Job OK (d4bc4101-1947-4d99-af4f-f6683cf4fcfd)
worker-1            | [2026-09-14 02:39:10,311][PID:299][INFO][rq.worker] Result is kept for 500 seconds
worker-1            | 2026/09/14 02:40:01 [worker_healthcheck] Received TICK_60 event from supervisor
worker-1            | 2026/09/14 02:40:01 [worker_healthcheck] Performing `RQ Worker Healthcheck` check for process name worker-0
worker-1            | 2026/09/14 02:40:01 [worker_healthcheck] WorkerHealthcheck: Worker rq:worker:885e815eedf14d348db13ff927a7d202 healthcheck: Is busy? False. Seen lately? True (51 seconds ago). Has nothing to do? True (0 jobs in watched queues). ==> Is healthy? True
worker-1            | 2026/09/14 02:40:01 [worker_healthcheck] `RQ Worker Healthcheck` check succeeded for process worker-0
worker-1            | RESULT 2
worker-1            | OKREADY
worker-1            | [2026-09-14 02:40:09,564][PID:45][INFO][rq.worker] default: abbf5b6d-aae6-486d-8c54-72fb8e1c45ed
worker-1            | [2026-09-14 02:40:09,785][PID:300][INFO][rq.worker] default: Job OK (abbf5b6d-aae6-486d-8c54-72fb8e1c45ed)
worker-1            | [2026-09-14 02:40:09,785][PID:300][INFO][rq.worker] Result is kept for 500 seconds
worker-1            | 2026/09/14 02:41:01 [worker_healthcheck] Received TICK_60 event from supervisor
worker-1            | 2026/09/14 02:41:01 [worker_healthcheck] Performing `RQ Worker Healthcheck` check for process name worker-0
worker-1            | 2026/09/14 02:41:01 [worker_healthcheck] WorkerHealthcheck: Worker rq:worker:885e815eedf14d348db13ff927a7d202 healthcheck: Is busy? False. Seen lately? True (52 seconds ago). Has nothing to do? True (0 jobs in watched queues). ==> Is healthy? True
worker-1            | 2026/09/14 02:41:01 [worker_healthcheck] `RQ Worker Healthcheck` check succeeded for process worker-0
worker-1            | RESULT 2
worker-1            | OKREADY
worker-1            | [2026-09-14 02:41:12,554][PID:45][INFO][rq.worker] default: a4d83df1-be86-4cb6-b9ef-719a6deb3cf4
worker-1            | [2026-09-14 02:41:12,637][PID:301][INFO][rq.worker] default: Job OK (a4d83df1-be86-4cb6-b9ef-719a6deb3cf4)
worker-1            | [2026-09-14 02:41:12,638][PID:301][INFO][rq.worker] Result is kept for 500 seconds