Connect to data

Ontology sync history

The Sync History page tells an ontology’s story with Microsoft Fabric. It starts with where the ontology came from, then lists every push to Fabric and every pull from Fabric, newest first, so you can see what changed, when, and who did it.

In the app: Data Context › Ontologies › your ontology › More › Sync history

[screenshot]

The Sync History page: the origin card on top and the runs grid beneath it, with one row expanded.

Open the page¶

Open the ontology from Data Context › Ontologies.
Click More and choose Sync history.

Anyone who can open the ontology can read its sync history. Back to Ontology returns you to the ontology.

The origin card¶

The card at the top records how the ontology was first created:

Title	Meaning
`Imported from file`	Uploaded from an ontology file. The file name is shown.
`Imported from Fabric`	Imported from a Fabric ontology item. The item and its workspace are shown.
`Standard import`	Imported from an industry standard. The standard and its version are shown.
`Created blank`	Started empty in Kenseme.
`Origin not recorded`	Created before Kenseme started recording origins.

Below the title you see who created the ontology and when.

When the Fabric source has moved on¶

For an ontology imported from Fabric, a chip next to the title warns you when the source has changed:

Out of sync — the Fabric ontology you imported has changed since. Your copy isn’t updated automatically; re-import it from Fabric if you want the newer version.
Source removed — the Fabric ontology no longer exists. Your copy keeps working with what you imported.

Other copies of the same source¶

If the same Fabric ontology has been imported more than once in your organization, the card lists the other copies under Also imported from this source, with a link to each and the date it was imported.

Diverged means that copy now syncs with a different Fabric item than the one it came from.
Never published means that copy has never been pushed to Fabric. These copies have a Delete button, so you can clean up accidental duplicates. You’re asked to confirm, and it can’t be undone.

The runs grid¶

Each row is one push or pull. If the ontology has never synced, you see No syncs yet instead.

Column	What it shows
(indicator)	An up arrow for a push to Fabric, a down arrow for a pull from Fabric, coloured by outcome, with how long ago it ran.
`Operation`	The kind of run.
`Version`	The version the run carried: a saved version such as `v1.4.0` when you deployed one, otherwise `Live`.
`Started` / `Completed`	When the run began and ended. A run still in progress shows `running`.
`User`	Who started it. Runs Kenseme started on its own show `system`.
`Status`	`Succeeded`, `Failed`, `Running`, `No changes`, or `Canceled`.
`Changes`	A compact tally of entities and relationships added, updated, and removed.
`Target`	The Fabric ontology item the run synced with.

Click a row to expand it. You see the run’s narrative (what it did, in plain language) and, for a failed run, the error message.

While any run is still Running, the page refreshes itself until the run finishes.

Retry a failed run¶

A failed run that belongs to a binding environment has a Retry button. It takes you to the lakehouse binding workspace on that environment and opens the matching push or pull preview, so you can fix what went wrong and run it again in context. See Sync an ontology with Microsoft Fabric.

The sync indicator on the ontology¶

The same arrow indicator appears next to the ontology’s name on its detail page, showing the most recent run. Hover over it for the detail, such as Pushed to Fabric · v1.4.0 · 2 hours ago. If the ontology has never synced, the indicator doesn’t appear.