Trace record provenance

Follow a stored result back to its producing sync or workflow run.

A record's source tells you how it entered Strive. Connector-sync records and workflow-derived records have different origins even when their visible content looks similar.

Start from the record

Open the record and inspect its source label. Use the source link to move toward the relevant connection or workflow context. A workflow-derived record points back to Workflows with its producing run as context. An ingested record points toward Connections so you can investigate the connected source.

The Data source group can be more specific than the record's source label: it can include the individual step that produced the output. Preserve that context when comparing records from different steps in one workflow run.

Investigate a changed result

Compare the producing run, step, creation time, and expected record type. Then inspect the workflow's inputs and step results. If the output came from synchronization, check the source's sync history and connection access at the time of the run.

A later credential change can expose a different account. A later provider edit can also change the original item. Neither action rewrites the provenance of an already stored record, so inspect the specific run rather than assuming today's provider state was yesterday's input.

Provenance and evidence

Origin identifies the process that produced a record. A citation identifies the supporting location in a document. A retained capture preserves the bytes used for a review or extraction. These are related but different kinds of information.

For an evidence-backed App table, open cell evidence to inspect the captured document and quote. A source link by itself does not prove that the value is correctly interpreted or that extraction found every relevant passage.

Continue with sync history, workflow guides, and document evidence.