Endless Cronjobs for Updating Campaign Action

Your software
My Mautic version is: 4.2.0 / 4.2.1
My PHP version is: 7.4
My Database type and version is: 10.3.34-MariaDB-0+deb10u1-log

Your problem
My problem is:

  • out of nothing suddenly my cronjob logs (for one occasion) exploded to 80GB and growing
  • reason was a never ending campaign build activity (see screenshot)
  • there was planned to be one contact added in increments of 300
  • still after 800k steps not finished

These errors are showing in the log:

  • none

Steps I have tried to fix the problem:

  • regenerated assets (m:a:g)
  • cleared cache
  • upgraded from 4.2.0. to 4.2.1
  • check schema (fine)

How can I find out, which contact is about to be added? Maybe this one has gone crazy?

Hello @dirk_s,

How many contacts do you have in Mautic?
How many segments do you have?
How many campaigns do you have?

Can you disable the current problematic campaign, is CRONjob still a problem?


Hi @pierre_a its only around 9k in this installation. 2 dozens of segments active, about 3-4 dozens of active campaigns. Of course - disabling the related campaign stops the issue. Cloning it and running the new one is also no problem.

I only get concerned, that the instance is somehow messed up and would like to find the root cause.

Hello @dirk_s ,
Couple of questions:

  1. how often you trigger your cronjobs?
  2. Do you have campaigns with jump to other actions inside? Is it possible that some of your actions got into a loop?


Hi @joeyk it runs every 2 min. The concerned campaigns have only one action for one or more segments. No jumps, no loops…

I now cloned all three concerned compaigns and deactivated them. The clones seem to work alright. So I guess it may be a random problem, which I can’t really debug. Starting the old campaigns will immediately cause the problem again.

Good that you could narrow it down.
I usually check like this:

  1. turn off cron.
  2. make sure it finished it’s job
  3. run the cron manually and check when it finishes. You can also see in ssh which campaign is the culprit and why:
  • does it have too many inactive items?
  • just simply too large and slow?
1 Like