Tasks no run after terminations

Author: alteestCreated May 11, 2026Updated May 13, 2026
Labelsbug

Things to check first

  • I have checked that my issue does not already have a solution in the FAQ

  • I have searched the existing issues and didn't find my bug already reported there

  • I have checked that my bug is still present in the latest release

Version

4.0.0a6

What happened?

We use v4.0.0a6 in one of our service and we run it in Azure k8s using spot instance. Such instances can be terminated and then started again and after several such termination we had an issue with running jobs. Actaully, nothing run. In logs on eny run time a lot f messages like

Skipping job ba619c59-35dd-4b8c-ae41-98b9e3abf14e because task 'task_method_name' has the maximum number of 1 jobs already running

Looks like after such unexected terminations something got broken. Our solution currently is to remove all tables (with use DB) and restart service again. There is no issue on services which are not use spot instance (without unexpected termination)

How can we reproduce the bug?

Try to shutdown service serveral time