Troubleshooting Issues That Occur Only in a Salesforce Sandbox Environment

When a Salesforce issue occurs only in a sandbox and not in production, the recommended first troubleshooting step is to refresh the sandbox to confirm the issue persists in a newly created environment.

When the Issue is Isolated to a Sandbox

It is a common misconception that behavior can be accurately compared between two sandbox environments created at different times or refreshed inconsistently.

Salesforce Support does not have visibility into an organization's internal development lifecycle, configuration changes, metadata deployments, or data modifications that may differ between sandbox environments.

As a result, Support cannot fully analyze or reconcile differences in setup, customizations, or data across multiple sandbox environments.

Salesforce documentation also notes the following limitation from the following Considerations:

"A sandbox isn’t a point-in-time snapshot of the exact state of your data. We recommend that you limit changes to your production org while a sandbox is being created or refreshed. Setup and data changes to your production org during the sandbox creation and refresh operations can result in inconsistencies in your sandbox."

Sandbox inconsistencies can occur due to:

• Point-in-time copy inconsistencies
• Missing relational data in Partial Copy sandboxes
• Metadata differences between environments
• Stale or outdated sandbox data
• Ongoing development activities

In some cases, sandbox data that enters an unexpected state may not be recoverable without a refresh.

Steps to Refresh a Sandbox

If an issue occurs only in a sandbox and does not impact production:

1. Verify when the sandbox was last refreshed.
2. Refresh the sandbox to determine whether the issue persists in a newly created environment.
3. If refreshing is not possible immediately, create a new sandbox of the same license type for comparison and validation.

Refreshing helps determine whether the issue is caused by:

• A temporary sandbox inconsistency
• Corrupted or incomplete copied data
• Metadata synchronization issues
• Product limitations related to sandbox creation

If ongoing development work exists in the sandbox, consider retrieving undeployed metadata before refreshing so it can be redeployed afterward.

If sensitive data should not exist in sandbox environments, consider using:

• Developer or Developer Pro sandboxes
• Partial Copy sandboxes with limited object selection
• Salesforce Data Mask to obfuscate sensitive information

If You Are Unable to Refresh

If you cannot refresh the sandbox:

• Create a new sandbox using an available sandbox license.
• Review existing sandbox usage and delete unused sandboxes if additional licenses are needed.
• Contact your Salesforce Account Team to discuss temporary or courtesy sandbox licensing options if appropriate.

If Product and Technology teams become involved in the investigation, one of the first requested troubleshooting steps will typically be to reproduce the issue in a newly refreshed or newly created sandbox environment.