Inbound event table data archiving and cleanup

  • Release version: Yokohama
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    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

    This feature in the Yokohama release enables ServiceNow customers to efficiently manage inbound event data by archiving and purging records older than a specified retention period. It helps control table size growth and maintain instance performance by using automated table rotation and cleanup processes.

    Show full answer Show less

    Key Features

    • Retention Policy and Table Rotation: Configure retention policies with table rotation on the auto-flush form to retain up to eight weeks of event data, segmented into eight preconfigured shards representing weekly data.
    • Processed Inbound Events Table Management: The DevOps processed inbound events table stores copies of events in the states "processed" and "ignored." Table rotation is automatically activated after 56 days of data accumulation to archive and clean up old data.
    • Scheduled Jobs and Table Cleaners: Two weeks after upgrading, a scheduled job is auto-enabled to run every seven days, activating table cleaners that purge inbound event records exceeding the age limit. Table cleaners target events in different states such as "new," "retry," "in-progress," "deferred," "processed," and "ignored," based on the age specified in seconds.
    • Auto-update Frequency: Table cleaners for "processed" and "ignored" events automatically update to run every 30 minutes when event data older than seven weeks exists and the scheduled job has been active for two weeks.

    Practical Benefits

    • Maintains optimal database performance by controlling inbound event table size.
    • Ensures compliance with data retention policies by automating archival and cleanup of outdated event data.
    • Reduces manual intervention through automated scheduled jobs and cleaners.
    • Provides flexibility to modify table rotation settings via System Definitions if customization is needed.

    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

    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, and table cleanup. A scheduled job is auto-enabled two weeks after you upgrade.

    Table rotation on processed inbound events table

    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
    Tip:
    To modify table rotation configuration, navigate to System Definitions > Table Rotation and open the record for DevOps processed inbound events table.

    Scheduled jobs and Table cleaners

    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.
    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
      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
      based on the value specified in the Age in seconds field against the value in sys_created_on field.
    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

    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.