Dhru Fusion Cron Job Issues: Common Causes and Fixes

If you're running a Dhru Fusion install and your cron jobs are failing, running late, or timing out halfway through, you're not alone — it's one of the most common support questions we see. Here's a rundown of the usual suspects and how to fix them.

1. PHP max execution time set too low

Dhru Fusion's cron jobs process API calls in batches, and on a shared hosting plan with a default max_execution_time of 30 or 60 seconds, larger batches simply get cut off mid-run. This shows up as jobs that "complete" but leave a chunk of orders unprocessed.

Fix: raise max_execution_time to at least 300 seconds in your PHP configuration (via .htaccess, php.ini, or your hosting control panel's PHP settings, depending on your setup). If you're on shared hosting and can't adjust this yourself, ask your host directly — this is exactly the kind of limit that differs between generic shared hosting and hosting actually tuned for Dhru Fusion.

2. Cron interval too short for your order volume

A 10-second cron interval sounds great in theory, but if your server can't fully process one batch before the next cron fire starts, you end up with overlapping executions competing for the same database rows — which often looks like random failures rather than a scheduling problem.

Fix: match your cron interval to your actual order volume and server capacity. Low-volume sites usually do fine on 30-60 second intervals; only drop to 10 seconds once you've confirmed your server handles a single batch comfortably within that window.

3. API rate limits from suppliers

Some upstream API suppliers throttle requests per minute. If your cron job fires faster than your supplier allows, you'll see intermittent "failed" statuses that have nothing to do with your server at all.

Fix: check your supplier's documented rate limits and pace your cron interval accordingly. Logging the raw API response (not just Dhru Fusion's parsed status) makes this much easier to diagnose — a 429 response code is unambiguous once you're actually looking at it.

4. IonCube / loader version mismatches

Dhru Fusion ships IonCube-encoded, and a server running an outdated IonCube Loader (or one that doesn't match the active PHP version) can cause cron scripts to fail silently — no error, no log entry, the job just doesn't run.

Fix: confirm your IonCube Loader version is current and matches your active PHP version. Worth checking any time you or your host upgrades PHP.

5. Database connection limits

On shared hosting with a low max-connections cap, a cron job running alongside normal site traffic can get shut out of the database mid-process, especially during busy hours.

Fix: either raise your database connection limit if your hosting plan allows it, or move to a plan/server with headroom built in for concurrent cron plus traffic load.

If you're troubleshooting a specific error and want a second pair of eyes, feel free to reach out — we host a number of Dhru Fusion installs and these five issues cover the large majority of what comes up.