Scaling with Workers - What happens if you force a cron script?

How do the workers work together and know which message to pick up?

is there anyway to put a prefix on the messages and allocate it to a worker?

Havent fully read what these name locks do either - is this the prefix?

Or we spin up a worker per batch once a worker has been a assigned a batch then kill the worker on completion of that batch … (donno how much the devops would like that haha)

This should limit the cron per worker
mautic:broadcasts:send --min-contact-id=0 --max-contact-id=2500
mautic:broadcasts:send --min-contact-id=2501 --max-contact-id=5000
… etc