Nothing recurring happens in WBAMS unless the scheduler runs: no invoices are generated, no reminders sent, no overdue service suspended, no customer reply imported. It is one cron job that runs every five minutes, and a second one for the mail import.

New in 1.5.0.

Scheduled automation arrives with this release, so an installation upgrading from 1.4.1 or earlier has no cron job yet. Nothing recurring runs until you add one.

Add the cron job

In cPanel, open Advanced → Cron Jobs and add one entry that runs every five minutes:

/usr/bin/php -q /home/USER/public_html/scheduler/scheduler.php
  1. Replace /home/USER/public_html with your installation’s real path.
  2. Confirm the PHP binary path. Some hosts use /usr/local/bin/php or a version-specific path such as /usr/local/bin/ea-php81.
  3. Set the schedule to every five minutes: under Common Settings choose Once Per Five Minutes (*/5 * * * *). If your host limits how often a job may run, use the shortest interval it allows; once an hour is the least that works.
  4. Save.

Each run does only what is due, and a task that is still running is not started a second time, so the short interval costs nothing. Queued email, ticket escalations and scheduled ticket actions go out on the next run. The day’s work — invoices, reminders, suspensions, the database backup, the daily report — starts on the first run in the hour chosen under Setup → Automation Settings, which is 9am until you change it. See Frequency.

Once a day is not enough.

The daily run only starts on a run that falls inside its hour. A job scheduled once a day at any other time never starts it — no daily report, no database backup, and System Health goes on saying the scheduler has not completed — and everything queued waits a day for the next run.

The command must name scheduler.php.

Earlier trees carried a cron.php in this directory, which 1.5.0 removes. A crontab naming the old file runs nothing and reports nothing.

The mail import

Only if customers reply to ticket emails, which they will. Add a second job on the same schedule, every five minutes:

/usr/bin/php -q /home/USER/public_html/scheduler/pop.php

Then configure the mailbox it collects from on each support department. The alternative is piping, which delivers instantly but needs mail-server configuration; see Mail import and piping.

Check the command-line PHP version

The PHP that cron uses is often not the PHP your website uses, and it is frequently older. Run this once:

/usr/bin/php -v

If it reports a version below the requirement, find the correct binary and use its full path in the cron command. A version mismatch here produces a scheduler that fails silently on every run.

Only if you trigger it over HTTP

Command-line cron needs no key and most installations should stop at the step above. If you must trigger the automation from a URL — an external monitor, a hosting panel with no cron — set a key in settings.php:

$cron_key = 'a-long-random-string';

Then call the endpoint with ?key= and that value. Without a valid key it answers 404, which is deliberate: before 1.5.0 anyone who could reach the URL could create invoices and capture stored cards.

Confirm it ran

  1. Wait five minutes for the next run, or run the command once by hand over SSH.
  2. Open Platform → System Health once the daily automation hour has passed. The “System Cron Tasks” warning goes when a daily run has completed, not before.
  3. Open the dashboard and check Last Automation Run shows a time rather than “Never”.
  4. Look at the Automation Overview counters — invoices created, reminders sent — and confirm they match what you expected for the day.
“Never” after a scheduled run means the job did not execute at all.

Check the cron log or the mail cron sends on failure. A wrong path or an unreadable PHP binary fails before WBAMS is reached, so nothing appears in the WBAMS logs.