9.2 Understanding EDD (External Data Descriptor) within a Application Connector

Each connector can have one or more EDDs. An EDD is the first processing step inside a connector. It reads data from the source file and passes it into the connector for further processing.

On the Data Ingestion Errors page, connectors are shown at the top level. When you expand a connector row, you can see the EDDs that belong to it.

9.1 Connector Level vs. EDD Level

Level	What It Shows	Where You See It
Connector level	The overall status of each connector in the pipeline	Main table on the page
EDD level	The individual EDDs within a connector and their error details	Shown when you expand or click a connector row

Note:

To differentiate between Connector errors and EDD errors, check the name displayed at the top of the error details table.

• If it shows a connector name, the errors are at the connector level
• If it shows an EDD name, the errors are at the EDD level

What Happens When a Connector Is Not Executed

If a connector was not executed during the pipeline run, the page shows the following:

What You See	What It Means
No entry (empty row) for the connector	This connector was not executed. It was skipped during this pipeline run.
NA shown for the EDD inside that connector	Because the connector did not run, the EDD inside it also did not run. The status shows as Not Available (NA).
Zero values for an executed connector	A connector that ran but had no errors will show zero counts, not NA.

Example: If a pipeline has five connectors and only three are executed:

• The first three connectors will show actual results, including record counts and errors
• The remaining two connectors will show no data (empty fields)
• Their EDD details will appear as Not Available (NA)

Note:

NA means the connector or EDD was not executed during that run. It does not indicate an error.

What Happens When Errors Occur at the EDD Level

If a record fails at the EDD stage, it does not move to the next step. The pipeline stops processing that record at EDD itself.

This means:

• The error is captured and stored in the EDD error table
• The record does not go to the connector
• The record does not reach the final target table
• Only EDD-level errors are shown for that record
• There will be no connector-level error for the same record

Example: A pipeline has 100 records:

• 20 records fail at the EDD stage → stored as EDD errors
• These 20 records do not move forward
• Only the remaining 80 records go to the connector stage