# SyteLine TaskMan Background Queue Calculator for Reports and Utilities

> Source: https://netray.co/tools/syteline-taskman-background-queue-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

See whether TaskMan can keep up with the reports and utilities your users submit, how big the backlog gets after the peak and how long it takes to clear.

## Category

syteline

## Erp

Infor SyteLine

## Audience

- ERP administrator
- SyteLine power user
- IT manager

## Tool

**Kind:** calculator

**Inputs:**

#### Tasks submitted per peak hour

**Key:** arrivals

**Type:** number

**Default:** 120

**Min:** 0

**Step:** 5

**Unit:** tasks/hour

**Help:** Count rows in Background Task History submitted in your busiest hour.

#### Average run time per task

**Key:** avg_min

**Type:** number

**Default:** 2.5

**Min:** 0.1

**Step:** 0.1

**Unit:** minutes

**Help:** Completion time minus start time from Background Task History, averaged over the peak hour.

#### Tasks processing at the same time

**Key:** slots

**Type:** number

**Default:** 4

**Min:** 1

**Step:** 1

**Unit:** slots

**Help:** Concurrency you observe on Active Background Tasks or have configured for your TaskMan setup. This tool does not assume a default.

#### Length of the peak

**Key:** peak_hours

**Type:** number

**Default:** 2

**Min:** 0.5

**Step:** 0.5

**Unit:** hours

#### Tasks submitted per off-peak hour

**Key:** offpeak

**Type:** number

**Default:** 30

**Min:** 0

**Step:** 5

**Unit:** tasks/hour

**Outputs:**

#### Queue capacity

**Key:** capacity_per_hour

**Expr:** slots * 60 / avg_min

**Format:** number

**Description:** Tasks per hour TaskMan can complete at this concurrency and run time.

#### Peak utilization

**Key:** utilization_pct

**Expr:** arrivals / capacity_per_hour * 100

**Format:** percent

**Primary:** true

**Description:** Above 100% the queue grows for the whole peak.

#### Backlog at end of peak

**Key:** backlog_after_peak

**Expr:** max(0, (arrivals - capacity_per_hour) * peak_hours)

**Format:** integer

**Primary:** true

**Description:** Tasks still waiting when the peak ends.

#### Time to clear backlog

**Key:** clear_minutes

**Expr:** backlog_after_peak / max(capacity_per_hour - offpeak, 0.001) * 60

**Format:** minutes

**Description:** Spare off-peak capacity drains the backlog. A huge number means off-peak load alone fills the queue and it never clears.

#### Approximate wait before a task starts

**Key:** approx_wait

**Expr:** if(lt(utilization_pct, 100), avg_min * (utilization_pct / 100) / (1 - utilization_pct / 100) / slots, 0)

**Format:** minutes

**Description:** Simple approximation, not an exact queueing model. Shown as 0 at or above 100% utilization; use backlog and clear time instead.

**Chart:**

#### Utilization and backlog vs tasks per peak hour

**Type:** line

**X:** arrivals

**From:** 20

**To:** 400

**Steps:** 30

**Series:**

- utilization_pct
- backlog_after_peak

**Disclaimer:** Run times and concurrency are your measurements. The wait figure is an approximation; real queues with long-running MRP or report jobs behave worse than the average suggests.

## Content

**Intro:** When users run a report or utility in SyteLine 9 or 10 on premises, the request is queued as a background task and TaskMan picks it up and runs it. This calculator shows whether that queue keeps up at your peak hour and how long the backlog lasts when it does not.

**Sections:**

#### How a report runs in SyteLine

**Body:** A user opens a report form, sets options and clicks Print or Preview. The request is written to the active background task queue; TaskMan picks it up, runs the task and the result is recorded in history. Active Background Tasks shows what is queued and running, and Background Task History shows each task's submission, start and completion after it runs, even if it fails. A task that never reached the queue has no history record, so a missing record points at submission, not at the report. Background Task Definitions hold the task names and executables that can be submitted or scheduled.

**Bullets:**

- Active Background Tasks: queued and running tasks
- Background Task History: start, completion and status per task (BGTaskHistory table)
- Background Task Definitions: which tasks exist and how they run

#### The queue math

**Body:** Capacity per hour = slots x 60 / average minutes per task. Utilization = arrivals per hour / capacity x 100. If utilization is over 100%, the backlog at the end of the peak = (arrivals - capacity) x peak hours. After the peak, the queue drains at capacity minus off-peak arrivals, so clear time = backlog / (capacity - off-peak arrivals) x 60 minutes. Under 100%, the approximate wait uses the rule wait = run time x u / (1 - u) / slots, where u is utilization as a fraction. It is a planning approximation, not an exact multi-server model, but it shows the important shape: wait rises sharply as utilization approaches 100%, so 80% is already uncomfortable.

#### Worked example

**Body:** With 4 tasks processing at once and 2.5 minutes average run time, capacity is 4 x 60 / 2.5 = 96 tasks per hour. At 120 submissions in the peak hour, utilization is 125%. Over a 2-hour peak the backlog grows by 24 per hour to 48 tasks. Off peak, 30 tasks per hour arrive, leaving 66 per hour of spare capacity, so the backlog clears in about 44 minutes. Users see this as reports that take 20 minutes to appear mid-morning. Cutting average run time to 1.8 minutes, by moving two heavy reports off peak, raises capacity to about 133 per hour and removes the backlog entirely.

#### Fixing a slow queue

**Body:** Read real durations from Background Task History, sorted by total run time, not by count: a few long jobs usually dominate. Move MRP, APS, cost rollups and large period reports to scheduled runs outside the peak using Background Task Definitions and scheduling. Check Active Background Tasks for items stuck in a running state that hold a slot, and find out why before restarting the TaskMan service. Look at the SQL behind the slowest reports: one missing index can turn a 30-second report into a 10-minute one. Only then consider adding concurrency, because more parallel tasks also means more load on the same SQL Server.

**Bullets:**

- Sort history by run minutes, not by number of runs
- Schedule heavy jobs off peak
- Clear stuck tasks before adding capacity
- Tune the slowest report queries

**Cta:** If your users want to ask SyteLine for an answer instead of queueing a report, we can add a private AI layer on your own servers that answers from live data with read-only access.

**Faq:**

#### How do I run a report in SyteLine?

**Answer:** Open the report form from the menu or search, set the range and option fields, then choose Preview or Print. The request goes to the background queue and TaskMan runs it. When it finishes, the output opens in the report viewer or goes to the printer or file you chose. You can follow progress on Active Background Tasks.

#### Why does my SyteLine report take so long to appear?

**Answer:** Either the report itself is slow or it waited in the queue. Compare submission time with start time in Background Task History: a large gap means queueing, which this calculator models. A long gap between start and completion means the report query or data volume is the problem.

#### Where can I see failed SyteLine background tasks?

**Answer:** Background Task History shows every task after it runs, including failures, with status and messages. If a task you submitted has no history record at all, it most likely never reached the active queue, which points to a submission or TaskMan service problem rather than a report error.

#### How many tasks can TaskMan run at once?

**Answer:** That depends on your TaskMan and server configuration, so this tool treats it as an input rather than assuming a number. Watch Active Background Tasks during a busy period and count how many tasks are running at the same time; use that observed value for the slots input.

## Search terms

how to run a report in syteline, syteline report, syteline reporting, syteline report viewer, syteline taskman, syteline background task, syteline report slow, background task history syteline

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