Skip to content

Start here

Manage app dependencies

Inspect resource references and protect apps that consume published outputs.

Apps can share workflows and consume outputs from other apps. A dependency is a live reference, not a copied resource. Before retiring an app or changing its published contract, inspect who depends on it.

Inspect an app's inputs

Open Data to see data-source ids, source kinds, referenced workflows or producing app/output pairs, record-type filters, and load or trigger behavior. Use Open on an available target to inspect it. Open Workflows for the workflows referenced by the app and Connections for resources used by their jobs.

A Missing workflow means a reference no longer resolves and needs replacement. Unavailable means the current lookup could not confirm the resource; retry before concluding that it was deleted.

Inspect consumers

Open the app's Apps consuming view when available. Each row is one cross-app dependency and identifies the consumer app, its data-source id, and the output it reads. A single app can have several dependency rows.

The list excludes self-references from the external deletion work list. An app reading its own output is not another app that must be retired before deletion.

Resolve a blocked change

If deletion or output removal is blocked:

  1. Read the named consumer and data-source ids.
  2. Open each consuming app with the required permissions.
  3. Rebind the source to a replacement published output, remove it and update dependent bindings, or retire the consumer if it is no longer needed.
  4. Save and verify the consumer's behavior.
  5. Return to the producer and retry the original change.

A dependency can belong to another member's app and therefore not appear in your own Apps list. Coordinate with its owner rather than assuming the dependency report is wrong or deleting the underlying workflow directly.

Retirement effects

Moving an app to Trash disables workflows exclusively used by it while keeping shared workflows enabled. Permanent deletion removes workflows and derived data only when no remaining App references require them. Retained resources are restored with the app before its retention deadline.

See Outputs, Trash and restore, and Builder source health.