From e0cd916988ebed6d01c26a4d3e9128aa2bf22a7d Mon Sep 17 00:00:00 2001 From: Ross Nordstrom Date: Sun, 19 Mar 2023 06:02:21 -0600 Subject: [PATCH] Docs: Add details about reusing a unique job id (#391) See: * https://github.com/samuelcolvin/arq/pull/138#issuecomment-523589365 * https://github.com/samuelcolvin/arq/issues/221 --- docs/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.rst b/docs/index.rst index eb6ad372..58af8221 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -136,7 +136,7 @@ Sometimes you want a job to only be run once at a time (eg. a backup) or once fo invoices for a particular company). *arq* supports this via custom job ids, see :func:`arq.connections.ArqRedis.enqueue_job`. It guarantees -that a job with a particular ID cannot be enqueued again until its execution has finished. +that a job with a particular ID cannot be enqueued again until its execution has finished and its result has cleared. To control when a finished job's result clears, you can use the `keep_result` setting on your worker, see :func:`arq.worker.func`. .. literalinclude:: examples/job_ids.py