# Why Is Epicor So Slow? A Kinetic Performance Checklist

> Source: https://netray.co/erp-help/why-is-epicor-so-slow-kinetic-performance-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

Epicor slowness usually comes from one of five layers: the client PC or browser, the network and VPN, the application server, SQL Server (blocking, missing maintenance, memory) or a specific heavy BAQ, dashboard or BPM. Find out whether it is everyone or one user, one screen or all screens, then work down the layers. If Epicor is hosted in Epicor Cloud, check the status page and your account contact before tuning anything.

## Kind

error

## System

epicor

## Erp

Epicor Kinetic

## Module

Performance / SQL Server / Client

## Query

why is epicor so slow

## Alternate Queries

- epicor kinetic issues
- is epicor kinetic down
- epicor kinetic slow screens
- epicor 10 slow performance

## Applies To

Epicor 10.x and Kinetic, on-prem, private cloud and Epicor-hosted

## Steps

### How to find the cause

**Items:**

- Scope it: one user, one site, one screen, or everyone? Note the time it started and what changed (upgrade, patch, new BPM, new BAQ, new users).
- Check whether it is down or slow. Open a simple screen such as a part lookup. If even that is slow, suspect the server, SQL or the network. If only one dashboard is slow, suspect the query.
- Test from the server or a machine on the server's network. If it is fast there but slow remotely, the problem is network, VPN or WAN latency.
- Check SQL Server: current blocking, long-running queries, CPU, memory pressure, disk latency, and whether index and statistics maintenance runs regularly.
- Check the Epicor application server: IIS app pool health, memory, recycling, and the server event logs.
- Review BPM directives and custom code on the slow transaction. A synchronous directive that calls external services or runs heavy queries slows every save.
- Review the slow BAQ or dashboard: remove unnecessary joins, add filters and parameters, and avoid returning all rows to the client.
- Change one thing at a time and measure before and after.

## Sections

### Client and network

**Body:**

Kinetic's browser and smart client depend on client CPU and memory, browser caching and a stable connection. A remote office over VPN will feel every extra round trip, especially in screens that make many small calls. Compare timings from inside and outside the network before blaming the server.

Clear the client cache, check for antivirus scanning the cache folder, and confirm the client version matches the server version after an upgrade.

### SQL Server and the application server

**Body:**

Most persistent slowness traces back to the database: blocked sessions, missing index maintenance, stale statistics, too little memory, slow disks, or a few expensive queries. Look at the actively running queries and wait types rather than guessing. Long scheduled tasks (MRP, costing, big reports) running in business hours are a frequent culprit.

On the app server, watch memory and app pool recycling. Slowness that starts at a fixed time of day often lines up with a scheduled job, backup or a sync.

**Code:**

-- Currently blocked sessions on SQL Server
SELECT session_id, blocking_session_id, wait_type, wait_time, status
FROM sys.dm_exec_requests
WHERE blocking_session_id <> 0;

### Is Epicor down?

**Body:**

For Epicor-hosted tenants, check Epicor's status communications and open a case if there is an outage. For on-prem and private cloud, confirm the IIS site, app pool, SQL service and the Epicor task agent are running, and that licensing and certificates have not expired.

Keep a baseline: how long a standard screen takes on a good day. Without a baseline every complaint is an opinion.

## Pitfalls

- Restarting services without capturing evidence hides the cause and the problem comes back.
- Tuning SQL while a synchronous BPM is the real cause wastes weeks.
- Running MRP or costing during peak hours makes everything look broken.
- Assuming all slowness is the network when only one dashboard is slow.

## Ai Angle

Netray's approach is to keep ERP queries bounded: an assistant that generates read-only, filtered queries over Epicor data avoids the unfiltered all-rows BAQs that often cause slowness. It can also summarise which saved BAQs and dashboards are used most, so you know which to tune first. It does not replace DBA tuning.

## Faq

### Why is Epicor Kinetic slow today?

**Answer:** Check scope first. If everyone is slow, suspect the server, SQL, a scheduled task or an outage. If one user or site, suspect the client or network. If one screen, suspect a query or BPM.

### How do I know if Epicor is down?

**Answer:** Try a simple screen, check from the server network, and check the hosting provider or Epicor status if cloud-hosted. For on-prem confirm IIS, SQL and task agent services.

### Can a BAQ slow down the whole system?

**Answer:** Yes. A heavy unfiltered BAQ or dashboard can saturate SQL and block others. Add filters, parameters and limit the columns returned.

### Does upgrading fix slowness?

**Answer:** Sometimes, but often not. Measure first. Upgrades also change client behaviour and can expose customizations that were fast before.

## Search terms

why is epicor so slow, epicor kinetic slow, epicor kinetic issues, is epicor kinetic down, epicor 10 performance, epicor sql server blocking, epicor slow dashboard, epicor kinetic performance tuning

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