From 65c6df99409a8bb90c29778e11db28fa831e73ec Mon Sep 17 00:00:00 2001 From: git_admin Date: Mon, 27 Apr 2026 08:46:27 +0000 Subject: [PATCH] Tower: upload queue_job 16.0.2.12.0 (via marketplace) --- addons/queue_job/readme/ROADMAP.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 addons/queue_job/readme/ROADMAP.rst diff --git a/addons/queue_job/readme/ROADMAP.rst b/addons/queue_job/readme/ROADMAP.rst new file mode 100644 index 0000000..34cc20e --- /dev/null +++ b/addons/queue_job/readme/ROADMAP.rst @@ -0,0 +1,18 @@ +* After creating a new database or installing ``queue_job`` on an + existing database, Odoo must be restarted for the runner to detect it. + +* When Odoo shuts down normally, it waits for running jobs to finish. + However, when the Odoo server crashes or is otherwise force-stopped, + running jobs are interrupted while the runner has no chance to know + they have been aborted. In such situations, jobs may remain in + ``started`` or ``enqueued`` state after the Odoo server is halted. + Since the runner has no way to know if they are actually running or + not, and does not know for sure if it is safe to restart the jobs, + it does not attempt to restart them automatically. Such stale jobs + therefore fill the running queue and prevent other jobs to start. + You must therefore requeue them manually, either from the Jobs view, + or by running the following SQL statement *before starting Odoo*: + +.. code-block:: sql + + update queue_job set state='pending' where state in ('started', 'enqueued')