---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# ECC queue growth

# Troubleshoot ECC queue growth {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
If the ECC queue keeps growing or contains large numbers of stale
synthetic monitoring messages, use this information
to identify why the auto-purge job isn't clearing them.

## The job reports success but the queue doesn't shrink

The most common cause of this condition is that the ECC Queue \[ecc_queue\] table doesn't have Can Delete application access enabled. This access isn't enabled by default, so until an admin grants it, the
job can evaluate messages against the purge categories but can't actually remove any of them.

Review the job's log output for warnings from the most recent run. If a
warning indicates that records couldn't be removed, confirm that the
job has delete access to the ECC Queue \[ecc_queue\] table. To grant that access, see [Enable ECC queue cleanup](https://www.servicenow.com/docs/roFTdn5niqmfu2nH1HUDTw "Grant the ECC Queue auto-purge job permission to remove old synthetic monitoring messages from the ECC queue.").

## Messages remain for monitors that are disabled

When a monitor is disabled, messages that it already placed in the
queue can remain there. On its next run, the auto-purge job flags
queued messages in the Ready or
Processing state as errored when the monitor
they belong to is disabled. Because the job runs once daily, these
messages can persist until the next run.

## Stale entries appear to be pending work

Messages left in the Ready state that were never
picked up, and messages stuck in the Processing
state, can look like pending work when they are reviewed in the queue.
The auto-purge job flags both as errored so that they are
distinguishable from messages that are genuinely waiting to be
processed. For the age thresholds that apply to each state, see [ECC queue auto-purge for synthetic monitoring](https://www.servicenow.com/docs/wtju73ueUQKItmzNuA8Cbw "A scheduled job removes old Synthetic monitoring messages from the ECC queue. The job also flags stuck or orphaned messages with status as error, so that the queue doesn't grow indefinitely and stale entries aren't mistaken for pending work.").