# How to Schedule a Background Task in SyteLine Task Manager > Source: https://netray.co/erp-help/syteline-task-manager-background-task-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SyteLine's Task Manager lets an administrator schedule recurring background work - an MRP or APS regeneration, a report run, a custom IDO method, or an external program - without a user triggering it manually from the client. You define a task with what to run and on what recurrence, and the Task Manager background service picks it up and executes it at the scheduled time. ## Kind advanced ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module Administration - Task Manager ## Query How to schedule a background task in SyteLine Task Manager ## Alternate Queries - syteline scheduled task not running - syteline task manager setup - schedule mrp run automatically syteline - syteline background job scheduler ## Applies To SyteLine 8.x, 9.x, CloudSuite Industrial (CSI) 10.x ## Steps ### Set up a recurring scheduled task **Items:** Open the Task Manager or Scheduled Tasks form in SyteLine, searching for it by name in the CSI search bar, to see currently defined and running tasks. Create a new task and choose its type: a built-in process such as MRP/APS regeneration or report generation, an IDO method call, or an external program. Set the recurrence pattern - one-time, daily, weekly, monthly, or a specific interval - and a time window that avoids peak transaction hours for heavy jobs like MRP. Assign the task to run under the correct account and site context, since some tasks, like MRP regeneration, are site-specific and need to run once per site rather than once globally. Set priority and any sequencing your environment needs, for example running cost rollup after a BOM change import, or MRP after inventory transactions post. Save the task and confirm the Task Manager background service is running - a correctly defined task simply never fires if that service is stopped. Check the task's execution history after its first scheduled run to confirm it completed successfully and within an acceptable time window before relying on it. For anything business-critical, such as nightly MRP or EDI processing, add external monitoring on the task's log or completion record, since a silently failed scheduled task can go unnoticed for days. ## Sections ### What kinds of work belong in Task Manager **Body:** Typical candidates include MRP or APS regeneration, usually run overnight or several times a day rather than on demand by users, scheduled report distribution, periodic EDI or integration batch jobs, and any custom IDO method representing a repeatable maintenance operation such as a nightly cleanup or a recurring cost recalculation. Contrast this with one-off interactive actions a user should trigger from the client - if a task only ever needs to run once, at a specific moment, on someone's request, it usually does not belong in a recurring schedule. ### Recurrence, timing, and contention with live users **Body:** Pick a recurrence and time window that avoids collision with peak order-entry or shop-floor transaction volume, since a heavy background job like a full MRP regeneration competes for the same tables and locks that transactional screens need. Stagger multiple heavy tasks rather than scheduling them all at the same off-hours time - they can still contend with each other even outside business hours, especially on a database server already under I/O pressure from other overnight jobs. ### Diagnosing a task that silently stops running **Body:** The most common cause is the Task Manager background service itself having stopped, often after a server reboot or patch left it not set to auto-start. Check service status first before assuming the business logic itself is broken. Other frequent causes are the account the task runs under losing a permission or its password expiring, or a prior run still being stuck and blocking the next scheduled occurrence from starting. The task's own execution history or log is the next place to check after confirming the service is up. ### Chaining and dependencies between tasks **Body:** Where one task's output feeds another - an import completing before a cost rollup runs, for example - simple time-based scheduling with a generous buffer between steps is more reliable in practice than trying to make a background job scheduler behave like a true workflow orchestrator. A genuine dependency is usually better modeled as a single IDO method or App Event chain that calls the next step directly once the first one finishes, rather than as two independently timed tasks hoping their windows never overlap. ## Pitfalls - Scheduling a heavy job like MRP regeneration during peak transaction hours, causing contention that slows order entry and shop floor screens for everyone. - Not noticing the Task Manager background service itself has stopped after a server reboot, so every scheduled task silently stops firing. - Running a site-specific task like MRP without confirming it is scheduled per site in a multi-site environment, leaving some sites never regenerated. - Assuming a scheduled task succeeded because nothing is throwing an error, instead of checking its execution history after setup and periodically afterward. - Chaining tightly time-dependent tasks with too small a buffer, so the second task sometimes starts before the first has actually finished. - Running scheduled tasks under a personal user account whose password later expires or who leaves the company, breaking the schedule with no obvious error message. ## Ai Angle ERPray can be asked directly whether last night's scheduled MRP run or EDI batch actually completed, by checking the task's execution history and surfacing anything that failed or ran long, instead of an administrator having to remember to open Task Manager every morning. It can also flag a scheduling change that looks likely to collide with peak transaction hours before it is saved, based on the task type and the site's typical usage pattern. ## Faq ### My task shows as scheduled but never runs - why? **Answer:** Check first whether the Task Manager background service itself is running on the server; this is the most common cause. If the service is up, check the task's own history for a stuck or errored prior run that may be blocking the next occurrence. ### Can I run an MRP regeneration for just one site on a schedule? **Answer:** Yes, MRP and APS regeneration tasks are typically site-specific, so in a multi-site environment you schedule a separate task per site rather than expecting one task to cover all sites. ### Can Task Manager call a custom IDO method I wrote? **Answer:** Yes - a task type that invokes an IDO method is a common way to run recurring custom logic, such as a nightly maintenance routine, without a user having to trigger it manually from the client. ### How do I know if a scheduled task is taking too long and overlapping the next run? **Answer:** Review the task's execution history for run duration against its scheduled interval. If a heavy job like MRP regularly runs close to or past its next scheduled start time, widen the interval or move it to a quieter window rather than letting runs stack up. ## Search terms syteline task manager, schedule background task syteline, syteline scheduled task not running, csi task manager setup, schedule mrp run syteline, syteline background job scheduler, syteline task manager service stopped, syteline recurring task --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json