Relationships and Last Used

Relationships show how platform objects depend on one another in a selected Environment. Last-used metadata shows recent runtime use for supported objects and powers explorer filters and badges.

Relationships

Open Relationships from an eligible Workflow, Connection, API Key, DropPoint, Cluster, or other supported object. The view shows the selected object, dependencies it uses, and dependants that use it as a tree.

Choose the relevant Environment. A Workflow revision, Connection value, publish, and authorization can differ by Environment, so a relationship in Test does not prove the same dependency exists in Production.

Use relationships before deleting, rotating, moving, or changing a shared object. The view is evidence of resolved platform references, not a guarantee about business dependencies outside Flowgear.

v2 Runtime Site Configuration references

The Configurations Node reads and writes Site Configuration values. A v2 Runtime Workflow can expose which configuration keys its design uses and whether it reads, writes, or does both. References inside nested Steps are included.

For Get, the authored Return names identify the keys. For Set, a literal Key can be identified, but a key calculated by an Expression cannot be resolved from the design alone. Keys are case-sensitive. Use this information when assessing a configuration change, while checking dynamic access separately; missing usage metadata does not prove that a key is unused.

Last used

Workflow, Connection, API Key, and other supported explorer records can include LastUsedTime. Used recently filters and badges currently treat activity within the last week as recent. Folder badges summarize recent objects below the folder.

Last used is operational metadata and is excluded from design change hashes. It does not create a Workflow revision when refreshed.

A missing or old value does not prove an object is safe to delete. Scheduled use, a disabled Workflow, an external consumer, an unreached branch, or retention gaps can all hide future or historical dependence. Combine last-used data with relationships, logs, ownership review, and a controlled disable period.

See also

See Audit Trail, and Workflow Logs Screen.