Cron Job Update - Mautic 2.0x

By DB Hurley · PUBLISHED July 08, 2016 · UPDATED July 08, 2016

If you have a self-hosted version of Mautic, then the updates to cron jobs in Mautic 2.0 definitely impacts you.

One of the areas that Mautic is improving upon is industry standardization.  Many of the terms used in Mautic before v1.4 were updated.  With this release, we brought the terminology and functionality of the cron jobs into line as well.

Here are the updated cron jobs:

  • path/to/php path/to/mautic/app/console mautic:segments:update
  • path/to/php path/to/mautic/app/console mautic:campaigns:rebuild
  • path/to/php path/to/mautic/app/console mautic:campaigns:trigger
  • path/to/php path/to/mautic/app/console mautic:emails:send
  • path/to/php path/to/mautic/app/console mautic:social:monitoring

If you're wondering which cron jobs these replace, Don has provided a great overview at

Watch the Video:


If you’d like to suggest a topic, please head over to the #support channel and message @imrodmartin.




Jesh. I spent a whole day messing around with this trying to get it to work. Googled and searched like crazy and feeling like a failure. THEN, this ROD guy's Minute long YouTube explanation cleared the skies and the angels from the heavens gave me a cron job I will never forget. Thank you sir for being such a grand teacher in a pile of crazy code.
Jorge H

I spent few days trying to fix my cron jobs issue. Thanks a lot for the video!

I have wasted my precious 15 days to fix up the cron jobs issue. Your YouTube revealed the details about cron jobs. Thanks for this informative blog which you have uploaded

I’m running on a Linux shared server and running PHP Version 7.0.7 and this is what error I keep getting. PHP Parse error: syntax error, unexpected ‘.’, expecting ‘,’ or ‘;’ in /home/usr/public_html/mautic/app/bundles/EmailBundle/EventListener/ProcessReplySubscriber.php on line 26 Now, line 26 shows this: const CACHE_KEY = self::BUNDLE.’_’.self::FOLDER_KEY; Any idea of what is wrong? I asked my host just now and this was their reply: “The error which you are receiving is due to the scripts you are using, please contact your developer to fix it”. I've made a post over here as well but I would like to get as many eyeballs on this as I can to help:

In reply to by Greg


Hi, I have the same problem, did you find a solution?
Ruth Cheesley

In reply to by maik


It would be sensible to post this up on the forums (see topic here: - then others can provide feedback
Maurizio Melandri

In reply to by Greg


Hi, I have the same problem with all cron job scheduled