Context

Our scheduling is currently limited to only one celery worker running concurrently. This significantly impacts performance. Our locking system can also cause workers to not do anything for nearly a second which isn't great either.

AC

• our scheduling can handle multiple concurrent celery workers
• our scheduling is more stable and can no longer break due to weird locks appearing without a timeout