DQE validations may not be triggered in Salesforce when the expected configuration, user permissions, object setup, or automation context does not allow the DQE validation process to run.
Common symptoms
- DQE validation does not run when a record is created or updated;
- validation results remain empty;
- the behavior affects only one object, page, profile, or user group;
- validation works in one Salesforce environment but not another;
- the issue appears after a deployment, package update, or sandbox refresh.
What to check first
- Confirm that the DQE package or integration is installed and active in the environment.
- Check that the relevant Salesforce object and fields are configured for DQE validation.
- Verify that the affected users have the required permissions.
- Review recent changes to page layouts, flows, validation rules, triggers, or automation.
- Compare the behavior between production and sandbox when possible.
Automation and configuration context
In Salesforce, validation behavior can depend on the object, field mapping, user permissions, page context, and automation path used to create or update records. A validation may work in one context but not another if the configuration differs.
When to contact DQE Support
If the issue persists, provide the Salesforce environment, affected object, affected fields, user profile or permission set, steps to reproduce, screenshots, timestamps, and any recent configuration or deployment changes.