Update Run
data_lineage.update_run
ActionGoogle Cloudconnection required
Calls datalineage v1 PATCH /v1/projects/{projectsId}/locations/{locationsId}/processes/{processesId}/runs/{runsId}.
Updates a run.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Data Lineage
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, location
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
location Location or region; taken from the connection when unset. | string | No | — | — | — |
process Process name or id. | string | Yes | — | — | — |
run Run name or id. | string | Yes | — | — | — |
body The GoogleCloudDatacatalogLineageV1Run resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
attributes | object | — |
displayName | string | — |
endTime | string | — |
name | string | — |
startTime | string | — |
state | string | — |
{
"attributes": {},
"displayName": "",
"endTime": "",
"name": "",
"startTime": "",
"state": ""
}Related Google Data Lineage nodes
See Update Run run in a workflow.
In a technical demo we add the Google Data Lineage connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.