SLM Background Task Manager Guide
The SLM Background Task Manager schedules and executes automated tasks within Safety Lifecycle Manager. These background processes run independently of normal user interaction, allowing SLM to perform recurring maintenance, updates, data processing and other scheduled activities automatically.
The scheduler can operate in both Linux and Windows environments. Linux uses a scheduled service and configuration file, while Windows uses Windows Task Scheduler to execute the required SLM background process at defined intervals.
This guide explains how the SLM Background Task Manager is configured, how administrators manage scheduled tasks, how the Background Queue Monitor provides task visibility and how the Reset Queue function can recover processing when a task becomes stuck.
What Is the SLM Background Task Manager?
The SLM Background Task Manager provides the scheduling and processing framework used for automated tasks within SLM.
Background tasks run independently of normal user activity and can perform recurring operations such as maintenance, system updates, data processing and other repetitive functions without requiring a user to initiate every action manually.
SLM includes tasks that can run on defined schedules, as well as background processes created by application activity. These tasks are placed into the SLM queue and processed by the configured scheduler.
For the wider server environment supporting these services, see the SLM On-Premise Hardware and Software Requirements guide.
Configuring the Background Scheduler in Linux
In the Linux environment demonstrated in the training, the SLM task scheduler is managed through a scheduled service and configuration file.
The scheduling format defines when a command should execute using fields for:
- Minute
- Hour
- Day
- Month
- Day of the week
- User
- Command
For SLM, the demonstrated scheduler is configured to execute every minute. The scheduled command runs PHP and passes the SLM index.php file together with the controller and CLI method required to analyze the SLM queue.
This recurring process checks the queue for tasks that are ready to execute.
The training also demonstrates stopping, starting and reloading the Linux scheduling service. Administrators should use the commands supplied for their deployed environment rather than assuming that service-control commands are identical across every Linux distribution or container image.
SLM Background Task Manager Configuration in Linux
On Windows, the SLM Background Task Manager relies on Windows Task Scheduler to execute the recurring background process.
The demonstrated task is created using the following general configuration:
- Task name: SLM Task Scheduler
- Run using the System account
- Run with highest privileges
- Trigger once and repeat every minute indefinitely
- Execute the PHP program
- Pass the SLM
index.phppath and required controller method as arguments
The training also disables the condition that restricts execution to AC power so the task can run regardless of that state.
Within the task settings, the demonstrated configuration allows a new task instance to run in parallel when another instance is already running.
After creation, Windows Task Scheduler provides controls to run, end, disable or enable the SLM scheduler task.
Managing SLM Background Task Manager Schedules
The SLM Background Task Manager also provides application-level management of scheduled processes through the System module.
Administrators can access these tasks through Background Task Manager and Manage Task Schedules.
The training identifies automatic SLM tasks including:
- Destroying idle accounts
- System cleanup processes
- Updating test groups
- Managing the notification agent
- Other scheduled background activities
These maintenance-related processes are typically scheduled for periods such as midnight or early morning to reduce disruption to normal users.
System administrators can also execute a task manually using the Run Task function or edit the task configuration.
The demonstrated edit options include changing the task name and execution order.
Using the Background Queue Monitor
The Background Queue Monitor provides visibility into tasks currently being processed by SLM.
System administrators can access it through the System module under Background Task Manager and Background Queue Monitor.
The monitor can show tasks in states including:
- Pending
- Running
- Completed
For completed tasks, the training demonstrates information including:
- Status
- Description
- Scheduled date
- Modified channel
- Task information
This allows administrators to review whether background processing is progressing normally and whether individual tasks have completed.
Regular SLM users can also monitor pending and running tasks from supported user modules using the background-task icon in the top toolbar.
Resetting a Stuck Background Queue
Occasionally, a background task can stop or remain idle because of code, network or other processing issues.
A stuck task can prevent later tasks in the queue from executing, making queue recovery an important administrative function.
The SLM Background Task Manager includes a Reset Queue feature for this purpose.
Administrators can access the function through:
System Module → Background Task Manager → Reset Queue
Executing the reset clears the idle task demonstrated in the training, allowing subsequent background tasks to continue processing.
The Reset Queue function should therefore be used when a task is preventing normal queue progression rather than as a routine way to clear active processing.
How Background Processing Supports SLM Operations
The SLM Background Task Manager supports several different parts of the application by moving recurring and potentially longer-running operations into background processing.
This same background-processing model appears elsewhere in the SLM technical environment. For example, search-index rebuilds create background tasks, allowing administrators to initiate an indexing operation without performing the complete process synchronously.
The SLM Search Indexing and Index Rebuild Guide explains how index rebuilds and automatic index updates use background processing.
Other maintenance operations may also need to be investigated alongside application-level logs. The SLM Application Maintenance guide covers IIS and PHP logging that can provide additional evidence when troubleshooting application behaviour.
Windows and Linux Scheduler Differences
The main difference between the Windows and Linux implementations is the operating-system mechanism used to trigger the SLM queue-processing command.
On Windows, the recurring task is configured through Windows Task Scheduler. On Linux, the training demonstrates a scheduled service and configuration file that execute the SLM processing command every minute.
In both cases, the objective is the same: run the SLM background-processing method regularly so that queued tasks can be identified and executed.
Administrators should therefore focus on two separate layers when troubleshooting:
- Whether the operating-system scheduler is running correctly.
- Whether the SLM background queue itself contains tasks that are pending, running, completed or stuck.
Distinguishing between these layers can help determine whether a problem originates with the scheduler that checks the queue or with a task already inside the SLM processing queue.
Maintaining Reliable Background Processing
The SLM Background Task Manager is an important administrative component because automated application processes depend on the scheduler and queue working together.
A practical administration approach should include:
- Confirming that the operating-system scheduler is active.
- Reviewing scheduled SLM tasks and their execution order.
- Monitoring pending and running tasks through the Background Queue Monitor.
- Reviewing completed task information where necessary.
- Using Reset Queue when a stuck task prevents subsequent processing.
These controls give administrators visibility across both scheduling and execution, helping them distinguish between a task that has not yet been triggered and one that has entered the queue but is not progressing normally.
For general background on Windows scheduling behaviour, administrators can refer to Microsoft’s Task Scheduler documentation. SLM-specific task names, arguments and configuration should continue to follow MSS documentation and the SLM environment being administered.
