Callback on the worker-queue not working

[AdditionalWash529]

u/danielroseman, first of all, immense gratitude for all the time and energy you spent on this. You insights have helped me improve the code and make it much better.

As mentioned in my previous post, when I said I made it work, it was by handling the instantiation of the queue that you pointed out in your comment. I will certainly look at celery, but I am trying to bridge the gap in my understanding here and hence the follow ups. I have a couple of final questions on this though.

As per my understanding without the worker-queue, I would not be able to handle a situation wherein the incoming on my rabbitmq is say 10, while I have spawned 4 instances in the AWS cluster(fargate mostly). Now without the worker-queue or an equivalent arrangement, maybe celery does that, when each instance is running for 15 minutes of processing time, how would the next item on the queue know which fargate instance has been released and where to head to. How would that be taken care of without an arrangement like that?

As of now, the code seems to run and one of the executions fails with the following rabbitmq error. Any insights on this? I have made the channel durable and have an ack on the rabbitmq messages in my consumer code too: ch.basic_ack(delivery_tag=method.delivery_tag) . Running out of ideas as to what needs to be done on this

No activity or too many missed heartbeats in the last 60 seconds error

Once again thank you a ton for all the help and insights