Managing job queue records to free up Salesforce data storage

Last updated: July 28, 2026

Overview

Job Queue records are created automatically when background processes run in your org, e.g. when policies are renewed. Over time, these records can accumulate and consume a significant amount of Salesforce data storage. Use this article to identify which Job Queue records are safe to delete and which to retain.

Records safe to delete

The following Job Queue records can be deleted without impacting your organization. To preserve useful diagnostic history, consider deleting only records that are two weeks old or older.

  • Completed jobs

  • Failed jobs with no retry

  • Failed jobs where the Retry Count is at or above 2

Records to retain

Don't delete the following Job Queue records, as they represent active or in-progress work the system may still need.

  • Pending jobs

  • Queued jobs

  • In Progress jobs

  • Failed jobs that are still within their retry attempts

Before deleting in bulk

Review the records you plan to remove before completing a bulk deletion. Pay close attention to failed job records, as they may contain information useful for diagnosing past issues.