# Epicor Task Agent Schedule Load Calculator

> Source: https://netray.co/tools/epicor-task-agent-schedule-load-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Calculate Task Agent utilization from recurring schedules, runtimes and slots, and find how many slots you need.

## Category

epicor

## Erp

Epicor Kinetic

## Audience

- Epicor administrator
- Epicor developer
- Basis and IT operations

## Tool

**Kind:** calculator

**Inputs:**

#### Recurring schedules

**Key:** schedules

**Type:** number

**Default:** 60

**Min:** 1

**Step:** 1

**Unit:** schedules

**Help:** Count each recurring report, BAQ export and process.

#### Average run time

**Key:** runtime

**Type:** number

**Default:** 4

**Min:** 0.1

**Step:** 0.5

**Unit:** min

#### Average repeat interval

**Key:** interval

**Type:** slider

**Default:** 30

**Min:** 5

**Max:** 240

**Step:** 5

**Unit:** min

#### Task Agent concurrent slots

**Key:** slots

**Type:** number

**Default:** 2

**Min:** 1

**Max:** 32

**Step:** 1

**Unit:** slots

#### Target maximum utilization

**Key:** target

**Type:** slider

**Default:** 60

**Min:** 30

**Max:** 90

**Step:** 5

**Unit:** %

**Help:** Leave headroom for spikes and ad hoc jobs.

#### Nightly heavy jobs

**Key:** heavy_min

**Type:** number

**Default:** 180

**Min:** 0

**Step:** 15

**Unit:** min

**Help:** For example MRP regeneration and large reports, total minutes per night.

**Outputs:**

#### Runs per day

**Key:** runs

**Expr:** schedules * 1440 / interval

**Format:** integer

#### Busy minutes per day

**Key:** busy

**Expr:** runs * runtime + heavy_min

**Format:** minutes

#### Average concurrent jobs

**Key:** avg_conc

**Expr:** busy / 1440

**Format:** decimal

#### Slot utilization

**Key:** util

**Expr:** busy / (slots * 1440) * 100

**Format:** percent

**Primary:** true

#### Slots needed at target

**Key:** need

**Expr:** ceil(avg_conc / (target / 100))

**Format:** integer

**Primary:** true

#### Slots to add

**Key:** gap

**Expr:** max(0, need - slots)

**Format:** integer

**Chart:**

#### Slot utilization vs repeat interval

**Type:** line

**X:** interval

**From:** 5

**To:** 240

**Steps:** 30

**Series:**

- util

**Disclaimer:** Uses daily averages. Jobs often cluster at the top of the hour, so peak queueing can be worse than average utilization suggests.

## Content

**Intro:** Recurring schedules pile up quietly. One more report every fifteen minutes and suddenly jobs queue and nightly processing overruns. This calculator turns your schedule count, runtimes and slots into utilization and shows how many slots you need to keep a safe margin.

**Sections:**

#### How to use it

**Body:** List the recurring schedules from System Agent or the Task Agent monitor and take an average runtime and interval. Add your concurrent slot count and any heavy nightly work in minutes. Choose a target utilization such as 60 percent. The tool reports runs per day, busy minutes, average concurrent jobs, utilization and the number of slots needed.

**Bullets:**

- Export the schedule list and compute averages by job type if they differ a lot.
- Count heavy jobs separately, since they dominate nightly load.
- Re-run after adding integrations or dashboards that refresh on a schedule.

#### The formulas

**Body:** Runs per day equal schedules times minutes in a day divided by the interval. Busy minutes equal runs times runtime plus heavy job minutes. Average concurrency is busy minutes divided by minutes per day, and utilization divides busy minutes by slot capacity. Slots needed divide average concurrency by the target utilization, rounded up. It is a utilization view, not a full queueing simulation.

#### Interpreting the output

**Body:** Utilization below roughly half usually means jobs start promptly. Between sixty and eighty percent, queues form at busy moments. Above that, delays compound and heavy jobs can push into business hours. The chart shows that halving the interval doubles the load, so check whether every thirty-minute refresh really needs to be that frequent.

#### Common mistakes

**Body:** Average utilization hides clustering when many schedules start on the hour. Stagger start times, move heavy work to quiet windows and avoid chains that all fire together. Also confirm that slots are not capped by server memory or database capacity, since adding slots without capacity just moves the bottleneck.

**Cta:** Netray can review your schedule estate and propose consolidation or staggering. The calculator works without any input from us.

**Faq:**

#### What is a Task Agent slot?

**Answer:** It is a concurrent execution capacity for scheduled and submitted jobs in the Epicor task agent configuration. More slots allow more jobs to run at once, subject to server and database resources.

#### Should I just add more slots?

**Answer:** Only if the server and database have headroom. Often it is cheaper to stagger schedules, lengthen intervals for non-urgent jobs and tune the slowest reports before adding capacity.

#### How do I get average runtimes?

**Answer:** Use the task monitor or system monitor history to see start and end times for past runs, then average by schedule or by job type. Use at least a few weeks of data.

#### Why does the model add nightly heavy jobs separately?

**Answer:** Heavy jobs like planning runs can occupy slots for long stretches and are not repeated at a fixed interval, so they are easier to reason about as a fixed block of minutes per night.

## Search terms

epicor task agent, epicor task agent slow, epicor system agent schedule, epicor recurring schedule, epicor task agent concurrency, epicor task agent queue backlog, epicor mrp schedule window

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json