2026-10-28 | FieldRat

Why deleted Salesforce fields still count toward your limit

You deleted a few custom fields, tried to create a new one, and Salesforce still says you are at the limit. Before deleting anything else, check whether those fields are waiting for permanent cleanup.

1. Confirm which limit is blocking you

Write down the exact error and object name. In Setup, open Object Manager and check that object's Object Limits. A full Case object does not mean the whole org is out of fields. Check the custom field limits by edition before planning more cleanup or an edition upgrade.

2. Review Deleted Fields

Open Fields & Relationships for the affected object, then Deleted Fields. Match the field API names against your retirement checklist. If a field was deleted accidentally, pause the cleanup and assess restoration while that option is available. Do not permanently erase it just to make the warning disappear.

3. Check whether cleanup is still running

In Setup, search for Background Jobs. Look for the job named "Cleanup of custom field data when a custom field definition is hard deleted". Its progress helps distinguish queued work from completed cleanup. Completion time depends on Salesforce's workload; there is no reliable instant-release promise.

If the job has finished but you are still blocked, capture the error, object, field names, and completion time for Salesforce Support. This gives them a specific cleanup issue to investigate. Keep the field inventory unchanged while you establish what happened.

4. Understand Erase and Purge before using them

Permanent deletion removes the recovery option. Before approving it, preserve the field definition and any required data, get the business owner's approval, and review integrations that may not appear in a metadata scan.

Salesforce also documents a Purge option in Salesforce Classic for Enterprise, Performance, and Unlimited editions. It is conditional: the object must be at least 75% of its allocation and have fields ready for hard deletion. It requires Customize Application and View All Data. It starts permanent cleanup; it is not a restore or an instant capacity upgrade. Check the official Purge requirements for your org.

Make the next cleanup less urgent

Keep a short retirement record: field API name, owner, reason for retirement, backup location, dependencies reviewed, and approval. Start the review before an urgent deployment needs the last available slot. An empty field may still support a seasonal process or an external integration.

FieldRat helps you review population and dependency evidence before retirement. It does not control Salesforce's deletion queue, and a scan result is not permission to delete. Use the field cleanup checklist to keep those decisions explicit.

Common questions