serverless/serverless · error · ServerlessError

AGENT_INSPECT_NAME_NOT_DESCRIBABLE

AGENT_INSPECT_NAME_NOT_DESCRIBABLE

Error message

Resource "${name}" (${resource.type}) is not describable -- its type isn't supported by "serverless agent inspect".

What it means

Error "Resource "${name}" (${resource.type}) is not describable -- its type isn't supported by "serverless agent inspect"." thrown in serverless/serverless.

Source

Thrown at packages/serverless/lib/plugins/agent/lib/select.js:159

      const validIds = resources.map((r) => r.logicalId).sort()
      throw new ServerlessError(
        `Unknown --name "${name}". Valid logical IDs: ${validIds.join(', ')}.`,
        'AGENT_INSPECT_UNKNOWN_NAME',
      )
    }
    if (matches.length > 1) {
      const candidates = matches
        .map((r) => `${r.stack}/${r.logicalId}`)
        .sort()
        .join(', ')
      throw new ServerlessError(
        `Ambiguous --name "${name}": it matches resources in multiple stacks (${candidates}). This isn't yet disambiguable by stack; rename the conflicting resource or select by category/service instead.`,
        'AGENT_INSPECT_AMBIGUOUS_NAME',
      )
    }
    const resource = matches[0]
    if (resource.category === 'other' || !resource.awsService) {
      throw new ServerlessError(
        `Resource "${name}" (${resource.type}) is not describable -- its type isn't supported by "serverless agent inspect".`,
        'AGENT_INSPECT_NAME_NOT_DESCRIBABLE',
      )
    }
    return resource
  })
}

/**
 * Dedup rule (fixed by category, not by flag order): a function's IAM role
 * policies are inlined under the function only when functions are in the
 * RESOLVED selection and iam is NOT -- checked on the union of both axes, so
 * `--iam --functions` and `--functions --iam` (and `--functions
 * --aws-services iam`) all produce the identical decision.
 */
function computeInlineFunctionRole(selected) {
  const categories = new Set(selected.map((r) => r.category))
  return categories.has('functions') && !categories.has('iam')

View on GitHub (pinned to b9d7ea51c8)

Solutions

1. Choose a resource whose type is supported by 'serverless agent inspect', or inspect this resource via the AWS CLI/console directly.

When it happens

Trigger: Thrown at packages/serverless/lib/plugins/agent/lib/select.js:159 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of serverless/serverless@b9d7ea51c8 (2026-08-13). Data as JSON: /api/errors/1df45f4801db1637. Report an issue: GitHub.