Use a Webuzo cron job to run a trusted application command on a defined schedule. A successful schedule entry only proves the job was saved; verify the command actually runs as the intended account and produces the expected result.
IN THIS ARTICLE
What you need before you begin
Confirm cron is permitted for the account and obtain the application documented command. Identify the correct executable path, working directory, runtime version and required environment. Check the server timezone and how long a normal run takes.
01 Schedule and troubleshoot a Webuzo cron job
- Open Server Utilities > Cron Job in the end-user panel and choose Add Cron Job.
- Use the displayed scheduling fields or common presets for your installed version. Review the saved schedule carefully; do not paste a six-field scheduler example into a five-field Unix-cron form.
- Enter the command with absolute executable and script paths. If the application requires a working directory, invoke its documented wrapper or command sequence in that directory.
- Configure a protected output log or the intended cron email destination. Avoid discarding all errors during initial testing and keep credentials out of command arguments where possible.
- Test the command once as the same account through authorized terminal access, or use a harmless controlled schedule when terminal access is unavailable.
- Allow one scheduled run to finish, then check output and application state. Set an appropriate interval and prevent overlapping runs using the application supported locking mechanism.
Why does a command work in my shell but fail on schedule?
Cron has a smaller environment and may start in a different directory. Use explicit paths and supply required nonsecret configuration through the application supported environment or wrapper.
Confirm the expected result
Check the time of an actual completed operation, not merely the presence of the cron entry. Verify that scheduled mail, cleanup or synchronization produces only the intended changes. Confirm logs are private and have a retention policy.
Troubleshoot unexpected results
For failures that occur only under cron, compare PATH, working directory, environment, permissions and the PHP or other runtime executable. If the job duplicates work, disable the schedule while checking overlap and application idempotency. Avoid running it as root merely to bypass an account permission problem.