Overview
When creating a new sandbox in Amperity, you may immediately see validation or schema errors that do not appear in Production.
This can be confusing and may raise concerns about hidden Production issues.
This article explains why this happens and how to resolve it.
Why Sandbox Errors Appear
When a sandbox is created, it copies the latest saved configuration state from Production.
It does not always include the most recently published or fully synced changes.
Because of this:
Recent Production changes may not be fully reflected in the sandbox
Schema or validation errors can appear in the sandbox
Production itself may still be completely healthy
This behavior is expected and does not indicate a problem with Production.
How to Resolve Sandbox Validation Errors
You can sync the sandbox with the latest Production state using Sandbox Validations.
Steps:
Open the sandbox
Go to Sandbox Validations
Click on each validation error
Select Update schema
Click Resolve
Once completed, the sandbox should be fully synced and ready for use.
Can You Prevent This from Happening?
There is currently no way to guarantee that all changes are fully synced at the moment a sandbox is created.
However, you can reduce the likelihood of validation errors by:
Ensuring recent Production changes are fully published and validated before creating a sandbox
Running Update schema → Resolve after sandbox creation to pull in any pending updates
Best Practices
Treat sandbox validation errors as expected after creation
Always review Sandbox Validations after creating a new sandbox
Resolve schema updates before starting development or testing
Confirm Production changes are finalized before sandbox creation when possible
Summary
Sandbox validation errors can appear even when Production is clean because sandboxes copy the latest saved configuration, not always the most recently synced changes.
Using Update schema and Resolve brings the sandbox fully up to date and resolves the issue.
Applies To
Sandbox environments
Sandbox Validations
Configuration and schema updates in Amperity