# Inspect an app's workflows and connections

The app workspace provides resource views so you can inspect the work behind the interface without guessing which workflow or connection supplies it.

## Workflows

Open **Workflows** to see each referenced workflow's name, status, trigger, latest run, and available actions. Select the relevant row or action to inspect the workflow itself. Data sources in the app definition determine which workflows appear here.

If a workflow is marked **Missing**, update the app's source in the builder to point to an appropriate existing workflow. Starting the app or reloading its frame will not recreate a deleted reference. If it is **Unavailable**, choose Retry; a transient read failure is different from confirmed absence.

An app with no workflow references shows an empty state. It can still display static content or another app's published outputs; the Workflows view is not an inventory of every possible app behavior.

## Connections

Open **Connections** to see connections read or written by the app's workflow jobs. The view shows provider, display name or id, and status when available. **Open** leads to the connection's own management view.

This list is derived from workflow references. It is not a separate list to which you add credentials. Configure a connection in Connections, and configure the app's optional provider choices under Parameters.

An **Off for this app** marker means the connector remains referenced by the workflow but is disabled by this app's parameter policy. Follow the Parameters link to enable or change it. Switching it off does not delete the connection.

## Check the whole chain

For missing app data, inspect source scope, workflow status, the relevant run, connector selection, and connection health in that order. A healthy connection does not prove a workflow produced the record types the component expects; a successful workflow does not prove the app is reading the intended run.

Use [Workflow sources](/docs/builder/workflow-sources) for read and trigger scope, [Connector policy](/docs/apps/connector-policy) for optional providers, and [Connections](/docs/connections/overview) for authentication and provider setup.
