# Cronjob Trigger Issues with Date/Time Based Campaigns

**URL:** https://forum.mautic.org/t/cronjob-trigger-issues-with-date-time-based-campaigns/22644
**Category:** Product Support
**Created:** [February 9, 2022, 12:13pm UTC](https://forum.mautic.org/t/cronjob-trigger-issues-with-date-time-based-campaigns/22644 "2022-02-09T12:13:43Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![mikew](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/mikew/32/5156_2.png) [@mikew](https://forum.mautic.org/u/mikew)
#### Post date: [February 9, 2022, 12:13pm UTC](https://forum.mautic.org/t/cronjob-trigger-issues-with-date-time-based-campaigns/22644/1 "2022-02-09T12:13:43Z")

</div>

I have noticed some very very strange behaviour with Mautic:campaigns:trigger when running a campaign that has an action based on a specific date and time.

I have the following cron setup for triggering campaigns:

```auto
10-59/15 * * * * sudo -u www-data php7.4 /var/www/mautic/bin/console mautic:campaigns:trigger

```

When watching the system log I can see that this cron is being triggered correctly, however it is not firing off campaign with date/time action.

If I go and run this manually or even put in a separate cronjob with -I [campaign\_id] it triggers perfectly.

Further investigation has bought my attention to a bigger problem I am having.

We are sending out huge Push and SMS campaigns that are taking long periods of time to fire off.  
Once one of these campaigns is being triggered I notice that the specific job is not able to be triggered and I am given

```auto
Script in progress. Can force execution by using --bypass-locking.

```

Any insights here ?
