Closed Soures888 closed 7 months ago
Hi,
It's documented here: https://arq-docs.helpmanual.io/#job-uniqueness
Hi @JonasKs, thank you for your answer. I have tested this, and it does not work for me. The issue with creating cron jobs using a unique ID is that if a job has already finished, the executor will not start it again because a job with the same ID already exists.
How can I prevent starting a new task if the latest one hasn't finished? For example, in my production environment, I have a function that needs to run every 15 seconds. In some cases, one of these runs can take longer than 30 seconds, and I don't want this function to double-execute.