Troubleshooting Scheduled Tasks

Logs

When Jadu Central runs its scheduled tasks, it logs information about the tasks executed to a log file. The file is located in the logs directory. When diagnosing issues with scheduled tasks, we recommend checking logs to help diagnose issues.

<install_path>/logs/scheduled_tasks_log

Troubleshooting

1. Check the user that runs the cron or Windows task. The user will need to be active when the task runs, and have write and execute permission on the Jadu installation directory.
2. Check the tasks are active. Task master will need to run every 10 minutes, the Rescheduler entry will also need to be running regularly for it to pick up and restart dormant tasks. The Rescheduler must be offset from the time Task master runs, or tasks will be continually reset before they can be run. On Windows installs, both the task and its trigger need to be enabled.
3. Check the end date and next run date values of content managed tasks in JaduScheduledTasks. Tasks that should never stop should have an end date of 0, or 01/01/1970. The next run date should be in the future. The values in JaduScheduledTasks can be viewed by visiting "Utilities" >> "System Information" in the Control Center.
4. Check the start path of the task. On Windows installs, go to the action tab in the properties panel of the scheduled task thats not running and double click on the action to bring up it's properties. In the start in section put the full path to the folder the scheduled task .bat file is in.
5. Check the other server. Tasks should only be run on one server in a clustered environment. Disable tasks if they are found running on a second server.
6. Check the rescheduler is being run If tasks are not being rescheduled after failing, check that the rescheduler job exists.