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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Inbound event table data archiving and cleanup

# Inbound event table data archiving and cleanup {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Inbound Event Table Data Archiving and Cleanup

The inbound event table data archiving and cleanup feature allows ServiceNow customers to manage and purge event data records effectively.
It includes configuring retention policies and utilizing table cleaners to maintain optimal database performance by archiving data beyond a specified duration.
Show full answer Show less  

## Key Features

* **Retention Policy and Table Rotation:** Configure a retention policy with table rotation to keep eight weeks of event data, ensuring effective data management.
* **Scheduled Jobs:** An auto-enabled scheduled job runs every seven days, activating table cleaners to manage records older than seven weeks.
* **Table Cleaners:** Two cleaners are specifically designed for processing states (Processed, Ignored) and others (New, Retry, In-progress, Deferred) based on the defined age in seconds.
* **Auto-updates:** The frequency of table cleaners updates automatically to every 30 minutes if specific conditions are met, enhancing data management.

## Key Outcomes

By implementing these features, customers can expect improved database performance, timely data archiving, and effective management of inbound events. The automated processes reduce manual intervention, ensuring that only relevant event data is retained, which ultimately supports better resource utilization within the ServiceNow platform.  
Use table cleaners on the inbound events table to purge event data records beyond a
specified period.
Configure
a retention policy with table rotation on the auto-flush form to manage table
size growth and archiving data beyond the specified duration.

## Data management {#dev-ops-archive-cleanup-events-table-records__section_tcr_st3_ppb}

The data management feature allows you to enable archiving and purging of inbound event data.
Database rotation and table cleanup
configurations
are enabled to ensure that eight weeks of event data is retained. Instance
performance is preserved using ServiceNow AI Platform features such as Database rotation, [table rotation](https://www.servicenow.com/docs/access?context=c_TableRotation&version=australia&pubname=australia-platform-administration&ft:locale=en-US), and [table cleanup](https://www.servicenow.com/docs/access?context=table-cleanup&version=australia&pubname=australia-application-development&ft:locale=en-US). A scheduled job is auto-enabled two weeks after you
upgrade.

## Table rotation on processed inbound events table {#dev-ops-archive-cleanup-events-table-records__section_jq2_m4s_2pb}

The DevOps processed inbound events \[sn_devops_processed_inbound_event_list.do\]
table contains copies of event data from the DevOps inbound events
\[sn_devops_inbound_list.do\] table, that is in state 'processed' and
'ignored'.  
The processed inbound events table has the table rotation feature enabled. In all, there are eight preconfigured shards, each containing a week's event data from the DevOps inbound event table. By default, once you have 56 days (7 days) (Duration) \*8 shards (Rotations) of data in the processed inbound table, table rotation is activated. For more information on applying table rotation, see [Apply table rotation](https://www.servicenow.com/docs/access?context=t_ApplyTableRotation&version=australia&pubname=australia-platform-administration&ft:locale=en-US)  
Tip:  
To modify table rotation configuration, navigate to System DefinitionsTable Rotation and open the record for DevOps processed inbound events table.

## Scheduled jobs and Table cleaners {#dev-ops-archive-cleanup-events-table-records__section_myb_yt3_ppb}

Important:  
A scheduled job is auto-enabled two weeks after you upgrade . The scheduled job will run every seven days and is deactivated after the last update.  
Scheduled jobs activate tables cleaners on the inbound events if either of the following scenarios are met:

* A week after you upgrade, and the processed inbound table has records older than seven weeks.
* Two weeks after you upgrade.
{#dev-ops-archive-cleanup-events-table-records__ul_wd4_jxm_nsb}  
The table cleanup feature for the inbound events table \[sn_devops_inbound_table\] has two cleaners that are part of the base system upgrade.

1. Table cleaners are activated and run on the inbound events \[sn_devops_inbound_table_list.do\] for events in the following states.
   * Processed
   * Ignored

   {#dev-ops-archive-cleanup-events-table-records__ul_pmt_vm3_ppb}based on the value specified in the Age in seconds field against the value in `sys_created_on` field.
2. Table cleaners are activated and run on the inbound events table \[sn_devops_inbound_table_list\] for events in the following states.
   * New
   * Retry
   * In-progress
   * Deferred

   {#dev-ops-archive-cleanup-events-table-records__ul_eqc_ym3_ppb}based on the value specified in the Age in seconds field against the value in `sys_created_on` field.

{#dev-ops-archive-cleanup-events-table-records__ol_lcq_vm3_ppb}  
Note:  
By default, table cleaners are run on the inbound events table for these states from the time the schedules jobs are activated. The default value in the Age in Seconds field is 4,838,400 seconds (56\*24\*60\*60).

## Auto-updates to table cleaner frequency {#dev-ops-archive-cleanup-events-table-records__section_qkx_bmj_ppb}

Events in states processed and ignored are backed up and copied to the processed inbound events \[sn_devops_processed_inbound_event_list\] table. By default, the process cleaners are auto-updated to an interval of 30 minutes or 1800 seconds, on the inbound events table, if the following conditions are met:

* Two weeks have passed since the scheduled job is active.
* The processed inbound event table has event data older than 7 weeks.
{#dev-ops-archive-cleanup-events-table-records__ul_ivg_5p3_ppb}

*[\>]: and then