After a Salesforce sandbox refresh, DQE configuration or access settings may need to be reviewed before validations work as expected. A sandbox refresh can change environment data, users, permissions, endpoints, and integration settings.
Common symptoms after a sandbox refresh
- DQE validations no longer run in the sandbox;
- DQE components or actions are not visible for some users;
- authentication or connectivity errors appear;
- field mappings or configuration appear incomplete;
- the sandbox behavior differs from production.
What to check first
- Verify that the DQE package or integration is still installed and active.
- Check user permissions, profiles, and permission sets.
- Review object and field access for the users affected.
- Confirm that endpoints, credentials, licences, or environment-specific settings are still valid.
- Check page layouts, Lightning pages, and component visibility settings.
- Compare the sandbox configuration with production when possible.
Configuration review
A sandbox refresh can copy or reset configuration in ways that affect integrations. Review any DQE-specific setup, field mappings, automation, and access settings before running validation tests.
When to contact DQE Support
If the issue persists after checking the sandbox configuration, provide the sandbox name, refresh date, affected object, affected users, screenshots, timestamps, and any difference observed between sandbox and production.