Cron jobs run scheduled commands for maintenance, queues and application tasks.
Applies to: PHP, cron and developer tools
Developer tools can alter application behaviour for every visitor. Test PHP, cron, environment and runtime changes on a staging copy where possible, and never store secrets in a public document root or support-ticket screenshot.
Before you start
- Sign in to the Customer Portal and open the affected hosting service.
- Take a current backup before changing website files, databases, DNS or application configuration.
Step-by-step
- Obtain the exact command and schedule from the application documentation.
- Open SiteWorx and choose Cron Jobs.
- Use an absolute path to PHP and the script.
- Capture or suppress output intentionally.
- Test the job and review logs.
Confirm the result
- The selected runtime or scheduled task is visible after reload and uses the intended version, path and timing.
- A controlled test completes without adding a new syntax error, fatal error or duplicate cron execution.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| A runtime or cron change causes an immediate error. | The executable path, version, syntax, environment or working directory is wrong. | Run the exact command manually where safe, capture stderr and restore the previous runtime or schedule before trying another change. |
| A scheduled task runs more than once or not at all. | Duplicate cron entries, timezone assumptions, locking or an invalid command are involved. | Review every matching entry, add logging and a lock where appropriate, and test with a temporary controlled schedule. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Store application secrets safely
- Run Node.js or Python applications
- Change PHP settings
- Change the PHP version
- SSH and SFTP availability on shared hosting
Last reviewed: 2026-07-18.
