Clear Cutover Get a quote

Epicor Kinetic · Administration

The Epicor Task Agent and System Monitor explained: how reports and processes run in the background

By Al Hasib Tamim, published 25 October 2026

Applies to: Epicor Kinetic and Epicor ERP 10.2. Screen names, menu paths, service names, and the level of access you have vary across releases, deployment models (SaaS Cloud vs. On-Premises/Hosted), and security group permissions. In SaaS Cloud environments, the server-side service is managed by Epicor and you will not have direct operating-system access to it. Validate any procedure in a pilot or staging environment before using it in production.

Short answer

The Task Agent is the Epicor background Windows service that picks up and executes queued work, such as SSRS reports, MRP, postings, and scheduled jobs. System Agent Maintenance holds the configuration Inside Epicor (schedules, server paths, and concurrency limits) that tells the Task Agent how to run. System Monitor is the screen where users and administrators view that work—what is scheduled, what is pending or active in Ice.SysTask, what has finished, and what error messages were logged in Ice.SysTaskLog.

Key facts

  • Many Epicor reports and processes do not run directly inside your browser tab; they run asynchronously in the background as tasks.
  • System Agent is the configuration record inside Epicor (System Agent Maintenance, stored in Ice.SysAgent). Task Agent is the Windows service (Epicor ICE Task Agent Service) that connects to that configuration and runs the tasks.
  • In on-premises environments, the Task Agent Windows service is managed by your IT team via the Epicor Administration Console. In SaaS Cloud environments, Epicor manages it for you.
  • System Monitor displays task records from Ice.SysTask (with parameters in Ice.SysTaskParam, logs in Ice.SysTaskLog, and rendered report outputs in Ice.SysRptLst).
  • Never edit or delete task records directly in the SQL database.

What happens when you Submit a report

  1. You open a report or process and choose your options (filters, date range, schedule, output format).
  2. You click Submit. Epicor writes the request and its parameters to the database (Ice.SysTask and Ice.SysTaskParam).
  3. If the task is set to run "Now", it enters a Pending state waiting for an available Task Agent thread. (If it is assigned to a future schedule, it sits on the Scheduled Tasks tab until its Next Run Time arrives.)
  4. The Task Agent picks up the Pending task, marks it Active, and executes the business logic. For an SSRS report, the Task Agent extracts the report dataset into temporary tables in the SSRS report database and calls SQL Server Reporting Services (SSRS) to render the PDF or Excel file.
  5. When rendering completes, the rendered output is stored in Ice.SysRptLst (visible on the Reports tab in System Monitor) and the task status moves to Complete on the History Tasks tab. In the Kinetic browser interface, Print Preview opens in the browser, while direct client/local printing is handled by the Epicor Edge Agent (or server-side network printing).

If a task stays stuck at step 3 (Pending) or step 4 (Active), see our dedicated troubleshooting guide on reports stuck in Active or Pending.

The four pieces, in plain terms

Piece What It Is Who Usually Manages It
Task One submitted job (stored in Ice.SysTask and Ice.SysTaskParam) Created by the user who submits a report or process
System Agent The configuration record inside Epicor (System Agent Maintenance) defining schedules, SSRS URLs, and Maximum Concurrent Tasks Epicor Administrator
Task Agent The background Windows service that polls the System Agent queue and executes tasks IT (on-premises) or Epicor Cloud Operations (SaaS)
System Monitor The screen showing Active Tasks, History Tasks, Reports, and Scheduled Tasks Any user with permission to view their tasks; admins can view all users and cancel

What you can learn from System Monitor

  • Whether your task is waiting (Scheduled or Pending), running (Active), or finished (Complete / Error on the History Tasks tab).
  • The exact error message or stack trace on the Activity Log / Task Log panel (read from Ice.SysTaskLog) if a task fails.
  • Rendered report files on the Reports tab (read from Ice.SysRptLst), allowing you to re-open or download a previously generated PDF without re-running the query.
  • Whether other users' tasks are also waiting, which tells you immediately if the problem affects one specific report or the entire Task Agent queue.

Why a Task may stay Pending (common causes)

Causes differ by environment, so treat these as things to check in order:

  1. The Task Agent Windows service is stopped or disconnected from the application server (on-premises).
  2. The task was submitted on a recurring schedule (such as Daily or Hourly) instead of "Now", so it is waiting on the Scheduled Tasks tab for its Next Run Time.
  3. Active tasks have reached the Maximum Concurrent Tasks limit set in System Agent Maintenance, so new tasks must wait in Pending until an active thread finishes.
  4. A hung or runaway Active task is holding an agent thread indefinitely.
  5. The task is assigned to a specific System Agent ID that has no active Task Agent service listening to it.

A safe first-response checklist

  1. Note the System Task Num (SysTaskNum), the task description, who submitted it, and the submission time.
  2. Open System Monitor and check both the Active Tasks and History Tasks tabs (enable "Retrieve All" if you are an administrator checking across users).
  3. Check the Task Log (Ice.SysTaskLog) in the lower detail pane of System Monitor for any error message before assuming the task is still running silently.
  4. Wait a reasonable time for heavy jobs (like MRP or a wide PartTran report) before assuming a fault.
  5. If only one report fails or times out, re-test with a narrower filter and check the report query (see our BAQ report timeouts guide).
  6. If all tasks across all users are sitting in Pending with zero Active tasks completing, contact IT (on-premises) to check the Epicor ICE Task Agent Service in the Epicor Administration Console, or open an Epicor Support case (SaaS Cloud).
  7. Cancel a task in System Monitor only if you have permission and know it is safe—be especially cautious with financial postings (see our AR/AP Posting Stuck & Review Journal guide).
  8. Never delete or update rows directly in Ice.SysTask via SQL.

For administrators (on-premises)

  • Document which server runs the Epicor ICE Task Agent Service and which System Agent ID (in System Agent Maintenance) it connects to.
  • Review the Maximum Concurrent Tasks setting on your System Agent task agent configurations so a handful of long-running reports cannot starve all other users.
  • If tasks fail or stall, check both the Task Log in System Monitor and the Windows Event Viewer (Application and Epicor Task Agent logs) on the server.
  • Schedule heavy batch jobs (MRP, Capture COS/WIP, multi-month reports) outside peak daytime hours.

Good habits for users

  • Make sure the Schedule field is set to "Now" when you want an immediate report preview; selecting a named schedule queues the report for later.
  • Use tight filters (specific date ranges, sites, or part classes) rather than running wide-open reports.
  • Do not click Submit five times in a row if a report takes 30 seconds—each click creates another Ice.SysTask record in the queue.

FAQ

What is the difference between the System Agent and the Task Agent in Epicor?

System Agent is the configuration record inside Epicor (managed in System Agent Maintenance) that defines schedules, paths, SSRS settings, and concurrency limits. Task Agent is the Windows service that connects to that System Agent configuration and actually executes the background tasks.

What is Epicor System Monitor?

It is the screen that displays queued, active, scheduled, and completed background tasks (from Ice.SysTask), task error logs (Ice.SysTaskLog), and generated report files (Ice.SysRptLst).

Why is my Epicor report stuck on Pending?

The most common causes are: the report was accidentally submitted on a future schedule instead of "Now", the Task Agent has reached its Maximum Concurrent Tasks limit because other heavy tasks are running, or the Task Agent Windows service is stopped or disconnected.

Where do rendered PDFs live in System Monitor?

Completed report outputs are stored in Ice.SysRptLst and can be reopened from the Reports tab in System Monitor until their Retention Days period expires.

Can I fix a stuck task by deleting it in SQL?

No. Never run direct SQL DELETE or UPDATE statements against Ice.SysTask. Always use System Monitor or official Epicor support procedures.

Why did my report finish in System Monitor, but nothing printed on my local printer in Kinetic browser UX?

In the Kinetic browser interface, direct local printing relies on the Epicor Edge Agent running on the workstation (or configured Server Printing). If the task shows Complete on History Tasks and the PDF opens from the Reports tab, the Task Agent and SSRS succeeded—check the workstation's Edge Agent service.

References

Cross-check against official Epicor documentation matching your release and hosting model:

  • Epicor Kinetic help: System Monitor
  • Epicor Kinetic help: System Agent Maintenance and Task Agent Service Configuration
  • Epicor Kinetic help: Epicor Edge Agent Installation and Printing Guide

Systems I work on