Dry Runs | Yext Hitchhikers Platform


Dry runs allow you to run a connector and view the results without actually applying the results to the account.

When a dry run is initiated, Yext will process the data flowing into the connector, including all selectors, transforms, and mappings. However, these updates will not be sent to Content. Rather, Yext will simply display the results of what changes would occur should the run be executed. Updates are only sent to Content once a dry run’s results are approved by the user.

Triggering a Dry Run

Any connector run can be initiated as a dry run. This can be set in the following ways:

  1. When manually triggering a run
  2. On scheduled runs
  3. By adding the query parameter dryRun=true when sending a request to the /trigger endpoint
  4. By adding the query parameter dryRun=true when sending a request to the /push endpoint

Reviewing a Dry Run

Once a dry run completes, it will be in the status “Ready for Review.”

The counts of data updates can be viewed in the Connectors UI, or via the API. In the UI, dry run results will be noted with a “Dry Run” pill, to easily distinguish them from updates made by actual connector runs. Detailed results of a dry run are available for download as part of the Results file.

A completed dry run can either be approved or abandoned. If a dry run is approved, the data will not be re-processed. This means that:

  1. Any changes to the connector configuration or source data made between initiating and approving the dry run will not be reflected in the account.
  2. If any content included in the dry run is modified between initiating and approving the dry run, the end result of the data in the account may not exactly reflect the displayed results of the dry run. For example, if Entity A was to be updated by the dry run, but then a user deleted Entity A before approving the dry run, Entity A would be processed as a new entity instead of an updated entity.

Dry runs can be approved or abandoned via the Connectors UI or via their respective API endpoints ( /approve or /cancel ).

Users have seven days after the dry run was initiated to approve or abandon the run. After seven days, the run is automatically abandoned. Any dry runs that are not in a status of Completed or Completed with Errors cannot be approved.


Certain fields may validate in the dry run but ultimately fail due to additional validation that occurs in downstream services. Specifically, categories and keywords fields may register in the dry run as successful, but fail validation when processed.