Sync History
Sync History shows what happened when DFS read from a connector. Use it to confirm that data arrived, diagnose partial runs, and collect evidence before downstream workflows use the data.
Open:
Data Integration > Sync History
Connector Detail may also show recent sync logs and throughput.
What to check first
For a new connector, confirm:
- a sync run exists;
- status is OK or the problem is understood;
- read count is greater than zero;
- written count matches expected accepted rows or points;
- failed count is reviewed;
- the run time matches the expected schedule;
- data quality is acceptable for the use case.
Sync fields
| Field | Use |
|---|---|
| Time | When the sync started or completed. |
| Connector | Which source produced the run. |
| Status | OK, partial, or failed. |
| Read | Records or points read from the source. |
| Written | Records or points accepted by DFS. |
| Failed | Records or points rejected or failed during processing. |
| Statistics | Additional run details when available. |
Status interpretation
| Status | Meaning | Next action |
|---|---|---|
| OK | The run completed successfully. | Check written count and data quality. |
| Partial | Some data was accepted and some failed. | Review failed rows, mappings, and validation rules. |
| Failed | The run did not complete. | Check connector status, source access, and error details. |
Read, written, and failed counts
Use count patterns to diagnose issues.
| Pattern | Likely meaning |
|---|---|
| Read is zero | Source query returned no data, topic was empty, file was empty, or source path is wrong. |
| Read is high, written is zero | Mapping, validation, target identity, or table write failed. |
| Read is high, failed is high | Source data shape or quality is not acceptable. |
| Written drops suddenly | Source changed, mapping changed, quota changed, or upstream system is stale. |
| Failed count grows over time | Source schema or value format may be drifting. |
Investigate a partial or failed run
- Open the connector detail page.
- Check recent errors.
- Check whether the connector is connected, warning, error, disabled, or syncing.
- Review mappings changed since the last good run.
- Check data quality trend.
- Open the Review Queue if rejected rows are being collected there.
- Ask the source owner whether source schema, units, file format, topic payload, or credentials changed.
Evidence to keep
When a sync issue affects a downstream workflow, record:
- connector name;
- sync time;
- status;
- read, written, and failed counts;
- source owner;
- suspected cause;
- action taken;
- whether the next run recovered.
Next step
Use Data Quality to decide whether the connector output is ready for downstream use.