We create and schedule a cron job directly through your hosting control panel — a straightforward, server-level scheduled task setup, distinct from a more involved custom automation script with its own monitoring and failure handling built in.
Cron job creation & scheduling
A cron job created and scheduled through your control panel — the straightforward version, not custom code.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to your hosting control panel’s cron job management
- The exact command or script the job should run, and its intended schedule
- Confirmation of what the job is meant to accomplish, so we can verify it’s actually working
This or something else?
| You need a straightforward cron job created and scheduled through your control panel | This fix covers it |
| You want a more involved custom automation script, with monitoring and documented ownership handling | Custom cron job creation & monitoring, in the Integrations & Automation bucket, the more comprehensive version |
| Your host’s control panel doesn’t offer cron job management at all | Worth confirming your specific hosting setup — WordPress’s own scheduling may be the more realistic alternative |
| An existing cron job has stopped running correctly | Worth describing the specific issue directly — likely a diagnostic fix rather than a fresh setup |
What we do
- Confirm the exact command and intended schedule
- Create the cron job through your control panel
- Verify it runs successfully on its first scheduled execution
- Check the job’s actual effect matches what it’s meant to accomplish
- Document the schedule and command for future reference
- Confirm no conflict with any existing scheduled jobs
What is included
- A cron job created and scheduled through your control panel
- Verified successful first execution
- Confirmed effect matching the job’s intended purpose
- A written note on the configuration
Not included
- Writing complex custom automation logic — this schedules a command or script you provide, not designing what it does
- Ongoing monitoring of the job’s continued success — a separate, more comprehensive fix if that’s what you need
- Fixing this if your host’s control panel doesn’t support the specific scheduling precision you want
- Ongoing maintenance as your site’s requirements change
Questions about this fix
What if my host's control panel doesn't offer cron job management?
That's a real limitation on some hosting plans — WordPress's own scheduling system (WP-Cron) would be the more realistic alternative in that case, worth discussing if this applies to your setup.
Is this the same as the more comprehensive custom cron job fix?
No — that fix builds custom automation logic with monitoring and documented failure handling; this is a more straightforward setup of a cron job you've already defined, without that additional layer.
Who's responsible for checking this keeps working over time?
Since this is a simpler setup without the monitoring layer of the more comprehensive fix, that ongoing check is yours — we verify it works correctly at setup, but continued oversight isn't included here.
Can I have more than one cron job set up at once?
Yes, if you have multiple jobs ready to schedule, we can set them all up as part of the same engagement.
Will this affect other scheduled tasks already running on my hosting account?
We check for conflicts with existing scheduled jobs as part of this fix, since overlapping or resource-competing jobs can cause unexpected behaviour.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.