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

**URL:** <https://forum.mautic.org/t/scaling-with-workers-what-happens-if-you-force-a-cron-script/27854>\
**Category:** Product Support\
**Created:** [May 1, 2023, 6:07am UTC](https://forum.mautic.org/t/scaling-with-workers-what-happens-if-you-force-a-cron-script/27854 "2023-05-01T06:07:27Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![tornmarketing](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/tornmarketing/32/11603_2.png) [@tornmarketing](https://forum.mautic.org/u/tornmarketing)\
**Post date:** [May 1, 2023, 7:26am UTC](https://forum.mautic.org/t/scaling-with-workers-what-happens-if-you-force-a-cron-script/27854/8 "2023-05-01T07:26:53Z")

</div>

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

---

_[View the full topic](https://forum.mautic.org/t/scaling-with-workers-what-happens-if-you-force-a-cron-script/27854)._