On this page

Where to see the deployment status in the Salesforce instance?

The tool itself displays the current deployment status every 60 seconds. Salesforce provides the UI to view the status of the last 30 deployments. Please follow the below navigations on the Salesforce instance:

  1. Log in to Salesforce.

  2. Click on Setup.

  3. Type Deployment in the Quick Find box.

  4. Search Deployment Status.

Detailed steps at MonitorDeployment.

How to generate a new security token?

  1. Log in to Salesforce.

  2. Access your Salesforce settings (Top right corner).

  3. Enter reset into the Quick Find search bar

  4. Click on Reset My Security Token.

  5. Click on Reset Security Token

  6. A new token would have been received in the mail.

Detailed steps at ResetSecurityToken.

Can I upload a zip file which is not downloaded from this tool?

Yes. It will update the status of components defined in a zip file.

What if you encounter the ‘Cannot deactivate matching rule because of active associated duplicate rule’ error?

The solution is to remove the dependent component from the component list while disabling and running disable with the subset of components first. Once that succeeds, you can carry on with the dependent component. For example, if you encounter the error ‘Cannot deactivate matching rule because of active associated duplicate rule’, it means that certain matching rules are associated with an active duplicate rule. So, you have to disable the duplicate rule first then you have to run disable for the matching rule afterward.

Getting “Permission Denied” error while running dxrt

Check if you have permission to run exe in the folder dxrt is downloaded to. The user account must have read, write, and execute permissions on the dxrt folder and dxrt executable.

Getting “dxrt” can’t be opened because Apple cannot check it for malicious software.” on MacOS

  • Check if you have permission to run exe in the folder dxrt is downloaded to “chmod 777 dxrt” will allow all permission for running

  • Once permissions are in place, execute ./dxrt –version, you will get a pop-up that it is blocked

  • Go to MacOS –< Settings –> Security & Privacy –> General Tab. There should be an option to Allow dxrt to run next to the message “dxrt is blocked from use because it is not from an identified developer”.

  • Rerun ./dxrt –version now, it will prompt you whether you want to run or not. Click open in the prompt.

My Antivirus/Windows Defender blocks/quarantines dxrt

  • Right-click on the folder dxrt is located in and provide read, write, and execute permissions.

  • If you have Windows Defender or other Antivirus software installed, they could block dxrt from running on your machine. Please add the dxrt folder in the exclusion/whitelist for the antivirus software before running dxrt.

  • If your system security settings are managed at the enterprise level, please request dxrt.exe and dxrt folder be included in the allowed list.

Getting error - Field Sales_Ops_Approved__c does not exist. Check Spelling on Validation Rules

This error occurs because the field “Sales_Ops_Approved__c” does not exist in the Opportunity object. This can happen when the validation rule was created earlier and then the field was deleted. The solution is to change the “Filter Criteria” in the validation rule and remove the condition where this field is involved.

Resolve "the requested resource does not exist" error when using Bulk API v2

When using Bulk API v2, the "requested resource does not exist" error can occur if the JDBC connection string's APIVersion property is set to an integer value such as APIVersion=62 instead of the Salesforce API version format APIVersion=62.0.

The CData JDBC driver does not validate or normalize API version values that omit the decimal component. As a result, it generates an invalid internal Bulk API v2 endpoint URL, causing Salesforce to return a NOT_FOUND response because the requested resource path does not exist.

Resolution

Update the connector's APIVersion property to include the decimal component (for example, APIVersion=62.0) and rerun the masking job.

Resolve "invalid_grant" or "invalid token" error when running dxrt with OAuth

The invalid_grant or invalid token error can occur if the refresh token used by dxrt has expired, been revoked, or been replaced by a newer refresh token. When Refresh Token Rotation (RTR) is enabled, Salesforce invalidates the previous refresh token each time a new one is issued.

Resolution:

  • If you use dxrt as a standalone application, upgrade to dxrt 2026.1.0 or later, which supports Refresh Token Rotation (RTR) and Proof Key for Code Exchange (PKCE).

  • If you use dxrt through the Continuous Compliance Engine, upgrade to version 2026.4.0.1 or later, which includes dxrt 2026.1.0.

  • Generate new OAuth credentials (an access token and refresh token), then rerun dxrt using the updated credentials.

Salesforce requires RTR and Proof Key for Code Exchange (PKCE). To learn more, see Salesforce Connected Apps & ECA Security Controls - Partner App FAQs.

Verify RTR and PKCE are enabled in your Salesforce organization

For instructions, see Verify RTR and PKCE are enabled.

Record-triggered flows remain active when using the --sf_objects option

In versions earlier than 2025.3.0, record-triggered Salesforce flows were incorrectly excluded from disable and enable operations when you targeted specific Salesforce objects by using the --sf_objects option. As a result, these flows remained active during masking runs.

Resolution:

  • If you use dxrt as a standalone application, upgrade to dxrt 2025.3.0 or later.

  • If you use dxrt through the Continuous Compliance Engine, upgrade to version 2026.4.0.1 or later.

Questions?

For any questions, bugs, or feature requests contact us at Delphix Support.

Last updated
Oct 14, 2026