Background Jobs
Understand automatic background work, review failures and use manual controls only when needed.
Background Jobs handles work that should continue after the page that started it has been closed, including scheduled publishing, queued mail, maintenance, package operations, imports and recovery work.
Automatic Processing
Micro CMS normally starts and continues supported background work automatically. You do not need to keep Admin open while a job is running.
Execution Capacity
On a Solo installation with PHP CLI execution, Process Capacity is the total concurrent worker pool. Operator Headroom is the part of that capacity kept free for work you start manually, so routine automation cannot use every available worker. It is not an extra worker. Routine Capacity limits routine automation. The Solo default is 2 Process Capacity / 1 Operator Headroom / 1 Routine Capacity.
Review The Queue
Open System → Background Jobs to see queued, running, completed and failed work. A queued job is not necessarily an error; it may be waiting for available execution capacity or a prerequisite operation.
Finished History
Deleting or clearing a finished job-history record removes that history entry only. It does not undo completed work, cancel another operation or remove failed records that Micro CMS is preserving for attention.
When Work Needs Attention
Open the job detail for the current error and use the action Micro CMS offers. Do not repeatedly submit the same operation while the existing job is still queued or running.
Hosting Scheduler Fallback
If Micro CMS reports that automatic processing is unavailable on the host, use the optional hosting-scheduler guide. Do not weaken PHP security settings simply to make a background job start.