Run Statuses

There are seven possible statuses for a connector run. The statuses most useful for troubleshooting are marked below.

In Progress

The connector is actively running. A progress bar shows an estimated percentage of completion. If the run is a dry run, a "Dry Run" pill will be visible.

Completed

The run completed successfully with no errors. No action needed.

Completed with Errors 

The run completed, but some entities failed to process. Check the Entity Errors tab to identify and resolve the failing entities.

Errors at the field level cause that entity's update to fail, but all other entities are processed normally. Common causes:

• Invalid field value (e.g., exceeding a character limit, unsupported date format)
• Missing required field

These failures are generally not connector-specific — attempting to upload the same data via the Entities API or Entity Edit UI would likely produce the same errors.

A Completed with Errors status also occurs in Default Mode when ETL diagnostics are present. This happens when a transform fails on a specific row value. Since no fields have been mapped yet at the transform stage, Yext cannot match the row to an Entity ID and drops the row entirely before mapping.

Note: In Comprehensive Mode, ETL diagnostics cause an Aborted status rather than Completed with Errors.

Failed 

The run failed before processing any entities — the total entity count will be zero. The connector could not successfully extract and parse source data.

Common causes:

• Incorrect URL for an API request
• Unsupported file format uploaded

Check your source configuration and correct the issue before re-running.

Aborted 

The run was prevented from executing. Check Run Errors to identify the cause. This status applies when:

• A Run Breaker was triggered (see the Run Breakers reference)
• The connector is in Comprehensive Mode and an ETL error occurred during the Transform or Load stage (e.g., a Function Transform timeout, an improperly configured Format Dates transform). Because Comprehensive Mode is destructive — deleting entities missing from a run — Yext aborts the run to prevent unintended deletions caused by rows dropped due to errors.
• The connector configuration is invalid

Any entities that were already processed before the abort are not reverted.

Canceled

The run was manually canceled by a user. Updates applied to entities before cancellation are not reverted — only the remaining updates are prevented.

Ready for Review (Dry Runs only)

The dry run has completed (with or without errors) and is waiting for a user to approve or abandon it. Users have 7 days to take action; after that, the run is automatically abandoned.

• Approve: Initiates the load step; the run returns to In Progress.
• Abandon: Discards the results; no changes are applied to the account.

See the Connector Run Modes documentation for more information.

Viewing Run Results

Navigate to the connector's activity log and click View Details for a given run to see results in the platform. Results can also be downloaded as a spreadsheet via Download Details.

Availability: Results are only visible in the platform for runs started after November 8, 2023, and are retained for one year after the run completes. For runs outside this window, use the downloadable results spreadsheet.

The Run Summary and Entity Overview sections update immediately after a run completes. The detailed results table below those sections may take a few minutes to appear.

Entity Results

The left side of the Entity Results tab lists all entities included in the run, with the following columns:

• Status — New, Updated, Deleted, Failed, or Unchanged
• External ID
• Name — reflects the entity's current name value in the Knowledge Graph; updates if the name is edited after the run
• Language Profile

The right side displays the data that was mapped to each field for a given entity, the final value after any transforms were applied (or attempted). This view can optionally be shown in JSON format. Errors are grouped by the entity field they apply to.

You will also be able to filter entity results for criteria like entity ID, status, etc. 

Entity Errors

A consolidated list of all entity-level errors from the run. Each row represents a single error on a single field on a single entity. The information mirrors Entity Results but surfaces all errors in one view for easier review.

Run Errors

Run errors are errors tied to the entire run rather than a specific entity, or errors that cannot be matched to an entity at all.

Examples:

• A Run Breaker is triggered
• API fetch error
• Transform execution error
• Empty Entity ID value

Resolving run errors is important to ensure no data is silently dropped. Comprehensive runs that encounter run errors will always abort to prevent unintended deletions.

Dry Run Results

All results from a dry run are visible in the standard results view. Entity Results and Entity Errors appear under labeled "Dry Run" tabs. There is only a single set of Run Errors for a dry run, since approving a dry run applies the already-calculated updates without re-running the connector.

View Current Content: A toggle in Dry Run Results lets you see the current field value alongside the proposed update, including whether an update was detected for each field.

Limitations

Exporting Current and Proposed Values

Exporting the current and proposed values of a field for a dry run is not yet supported.

Labels and Folders

There is a temporary disconnect between what is shown in run results and what was provided as the value for a label or folder. The connector interprets provided values as display names, but the run results currently display the external ID of the corresponding display name. This behavior will be updated to show the display name in the future.

For dry runs, note that the external ID shown may differ from the final value if account changes are made between initiating and approving the dry run.

List Fields

If Add to Existing is selected for a list field, only the newly provided value(s) will appear in run results, not the full resulting list.

If multiple rows are ingested for the same entity ID, only the final processed row is shown in the results. Rows with a list exploded across multiple rows won't all be displayed, but the final entity will contain all values.