Configure task schedules and time templates
Administration schedules recurring tasks and exposes execution evidence. Business rules/scope remain in their modules.
Before configuration
Create the business task and agree interval, dates, and maintenance windows. Prepare templates for restricted dates first.
Create templates
- Open Task Management > Time Templates > New.
- Enter information and allowed dates, importing through the provided template if needed.
- Check month/year boundaries and holidays.
- Reference it in scheduling.
Templates support editing, enabling, disabling, and deletion. Referenced templates can still be disabled/deleted; tasks then lose those restrictions. Review affected tasks first.
Set recurrence
- Find the task and select Schedule.
- Enable/disable scheduling. Disablement does not terminate a current process.
- Set repeat interval.
- Choose time filters and verify allowed dates.
- Save/reopen and inspect the next eligible execution.
Allowed dates must satisfy templates and recurrence. Multiple templates use their intersection. For example, weekday and trading-day templates permit only dates in both sets; these are illustrative, not built-in templates.
Inspect execution
Review time/status and open the run's Log. Return to the business module to verify actual harvested objects or quality reports after scheduling success.
Monitor services
Task Monitoring shows nodes, memory, processes, tasks, and logs. Operations should assess impacts before force-terminating a process. Task Files registers files for task services; check dependencies and actual use after uploading.
Troubleshoot
| Symptom | Check |
|---|---|
| Did not run | Enablement, interval, allowed dates/intersection |
| Ran on unexpected dates | Disabled/deleted/changed templates |
| Failed | Logs, connections, files, business settings |
| Runs indefinitely | Service/process evidence; operations decides termination |
| Success, incomplete output | Business scope and per-object failures |