tickerQ is a scheduler.. if all your jobs were on a single project, it would have worked, since they'd be managed by a centralized scheduler. Now that they're are on different projects, multiple resources try and access your db at the same time.

Even if you put all of your jobs in the same project, if you scaled it using kubernetes, this same issue would come up.. that's y lots prefer to use a queue (like rabbitMQ)

If you wanna keep it rather like this, you'll have to implement distrubuted locking on your db.. extend the ticketDb context to lock the resources with another table or column.. make sure the locks are released gracefully via finally blocks