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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Enable ECC queue cleanup

# Enable ECC queue cleanup for synthetic monitoring {#ariaid-title1}

Release version: Australia  
Updated August 21, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Grant the ECC Queue auto-purge job permission to remove old synthetic monitoring messages from the ECC queue.

## Before you begin

Role required: admin

## About this task

The [ECC Queue auto-purge job](https://www.servicenow.com/docs/o2HWesRT6pMX4rRi3D_L4w "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.") requires Can Delete application access on the ECC Queue \[ecc_queue\] table. This access is not enabled by default. Until an admin grants it, the job can evaluate messages against its purge categories but cannot remove them.

Consider enabling this access as a performance-tuning step if you observe contention or delays in responses from synthetic monitoring checks, since an unpruned queue can contribute to that behavior.

## Procedure

1. Navigate to System DefinitionTables.
2. Open the ECC Queue \[ecc_queue\] table.
3. In the Application Access related list, select Can Delete.
4. Save the table record.
{#enable-ecc-queue-cleanup__steps_enable_cleanup}

## Result

On its next scheduled run, the ECC Queue auto-purge job removes and flags messages according to its [purge categories](https://www.servicenow.com/docs/o2HWesRT6pMX4rRi3D_L4w "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.").

## What to do next

Note:  
Enabling this access is a manual step in this release. Automating it is planned for a future release, so this procedure may be removed once that work ships.

*[\>]: and then