When creating a new sandbox in Amperity, you might see validation or schema errors right after setup. This doesn’t mean something is wrong with Production. These errors usually appear because the sandbox copies the most recently saved Production configuration, not the most recently published one. If recent changes in Production weren’t fully synced or validated before sandbox creation, the sandbox may show temporary errors.
How to Fix:
Go to Sandbox Validations in your Amperity tenant.
Click on each error and select “Update schema.”
Then click “Resolve.”
This will sync your sandbox with the latest Production settings. Once completed, the errors should clear automatically.
Best Practices:
Before creating a sandbox, make sure all recent Production changes are published and validated.
After creating a sandbox, always run “Update schema → Resolve” to sync any pending updates.
These steps ensure your sandbox reflects the latest Production setup and avoids temporary validation mismatches.
Expected Behavior:
This is normal and documented behavior in Amperity. The sandbox creation process may temporarily surface validation errors if there are unsynced schema or configuration updates in Production.
For more details, see the Amperity documentation on sandbox configuration and schema validation - docs.amperity.com/operator/sandbox_open.html .