Analyze resource
analyze_resourceCheck whether a resource and everything it depends on is sound — the deployability question. Pass 'hypothetical' to preview a change instead: hypothetical='delete' or 'unpublish' reports what would break WITHOUT changing anything (run it before deleting something other resources may use), and hypothetical='publish' checks whether the draft you are about to publish actually resolves. An APP is the usual subject: it walks every root the app contains (endpoints, schedules, domains) to the end of each chain and reports what would break. Returns findings {resource, path, severity, check, message}: errors are broken now (a reference that does not resolve, a dependency never published, a declared domain that routes elsewhere), warnings are risks (a published resource following @latest, a sub-workflow call cycle, a domain not yet verified), info is advisory. deployable is true when there are no errors. Also reports incomplete_nodes: resources whose references are built at run time and so cannot be checked statically. For a non-root subject like a workflow, analysis starts there rather than from whatever reaches it, so severities are not weighted by reachability.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | the kind of resource to analyze: app, dynamic_endpoint, schedule, custom_domain, workflow, api_template, datafile, schema, secret. An app is the usual subject | |
| resource | Yes | slug of the resource, optionally with a version suffix (e.g. 'shop/storefront' or 'shop/storefront@latest'); a bare slug means @published. For a custom_domain this is the hostname | |
| hypothetical | No | instead of checking the resource as it is, evaluate a change you are considering: 'delete' or 'unpublish' report what would break (nothing is changed — this is a preview), 'publish' checks whether the DRAFT resolves and flags what already follows this at @published. Run this before a delete or a publish |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| infos | Yes | ||
| errors | Yes | ||
| subject | Yes | ||
| findings | Yes | ||
| warnings | Yes | ||
| deployable | Yes | ||
| incomplete_nodes | Yes | ||
| reachability_known | Yes |