> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zwiron.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lineage

> Trace table and column lineage between Catalog assets after Jobs and Match write-back — upstream, downstream, and empty-graph fixes.

**Lineage** shows how data flows between Catalog assets. After Jobs sync tables—and after Match write-back when a project is linked to an asset—Zwiron records edges so you can see upstream producers and downstream dependents.

***

## Open Lineage

1. Select **Know → Lineage** in the application sidebar, or
2. Open an asset in **Know → Catalog** and use the lineage entry when available

Search or select an asset, then inspect **upstream** (what produces this asset) and **downstream** (what depends on it).

***

## What is recorded

| Level | Description | Typical source |
| - | - | - |
| **Table lineage** | Dataset-level producer → consumer edges | Completed Jobs; Match write-back to a linked Catalog asset |
| **Column lineage** | Field-level edges when mappings are known | Job column maps; transforms that rename or derive columns |

Lineage is strongest when:

* Connections are **profiled** into the Catalog
* Assets exist and are searchable under **Know → Catalog**
* Jobs or Match write-backs **complete successfully**

```
Source table ──Job sync──▶ Destination table
                              │
                              ▼
                         Match write-back (optional)
                              │
                              ▼
                         Golden / curated asset
```

***

## How to use Lineage

1. Open **Know → Lineage**.
2. Select or search for an asset (for example a Snowflake table created by a Job).
3. Inspect upstream sources and downstream dependents.
4. Drill into **column lineage** when debugging transforms, renames, or Match survivorship fields.
5. Use the graph before dropping a table or changing a Job so you know what breaks.

***

## Empty or incomplete graphs

| Symptom | Likely cause | Fix |
| - | - | - |
| No nodes | Asset never synced / not in Catalog | Profile the connection; confirm the asset in Catalog |
| Asset exists, no edges | Job or write-back not linked to Catalog | Re-run the Job after profiling; link Match project to a Catalog asset before write-back |
| Table edges only | Column maps unavailable | Check Job column selection and transforms; re-sync |
| Stale edges | Schema renamed or Job deleted | Re-profile and re-run; open Catalog for current names |

<Note>
  Lineage is an impact view over recorded moves — it does not invent edges from undocumented external ETL. Prefer Zwiron Jobs for automatic lineage.
</Note>

***

## Related articles

* [Know overview](/know/overview)
* [Catalog](/platform/catalog)
* [Jobs](/platform/jobs)
* [Match write-back](/match/write-back)
* [Transforms](/concepts/transforms)
* [Catalog and quality after sync](/guides/catalog-and-quality-after-sync)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.