error list

The error list command retrieves detected runtime issues (errors) across your deployed functions and containers. It shows each issue's error message, type, function name, project, stage, occurrence count, status, and last occurrence timestamp. Use it to inspect error patterns and occurrence counts from the terminal.

Usage

List all issues with default settings (returns up to 25 issues when no limit is provided):

stacktape error list

List open issues for a specific project and stage:

stacktape error list --project my-app --stage production --status OPEN

Flags reference

stacktape error listCLI options
-h, --helpstring

Show Help

If provided, the command will not execute and will instead print help information.

--status"OPEN" | "RESOLVED" | "IGNORED"

Issue Status Filter

Filter tracked errors by status (OPEN, RESOLVED, IGNORED).

--limitnumber

Limit

Maximum number of items to return.

--log-level"info" | "debug" | "error"

Log Level

The level of logs to print to the console.

  • info: Basic information about the operation.
  • error: Only errors.
  • debug: Detailed information for debugging.
--projectstring

Project Name

The name of the Stacktape project for this operation.

Commands that target a stack take it from projectName in the project's config when the flag is absent.

--quietboolean

Quiet

Hide progress, banners, success messages and hints. Command output, warnings and errors are still printed.

-s, --stagestring

Stage

The stage for the operation (e.g., production, staging, dev-john). You can set a default stage using the defaults set command. Stage names use lowercase letters, numbers and dashes, with at least 2 characters. The project name, a dash and the stage form the CloudFormation stack name, which can have at most 128 characters. Stacktape shortens an AWS resource name that would be too long and adds a hash.

Examples

Return up to 100 issues:

stacktape error list --limit 100

List only ignored issues:

stacktape error list --status IGNORED

Get JSON output for scripting or AI coding assistants. In agent mode, the command prints the returned issues as a pretty-printed JSON array instead of a table.

stacktape error list --agent --project my-app --stage production

Output

In interactive mode, the command prints a table with the following columns:

ColumnDescription
IDUnique issue identifier (used with other issue commands)
StatusOPEN, RESOLVED, or IGNORED
ErrorTruncated error message (up to 60 characters)
TypeError type or class name
FunctionName of the function or container that produced the error
ProjectProject name
StageStage name
CountTotal number of occurrences
Last seenTimestamp of the most recent occurrence

When no limit is provided, the command requests 25 issues. Omit --project, --stage, or --status when you do not want to narrow by those fields.

  • error resolve — Mark an issue as resolved. The issue reopens automatically if the same error occurs again.
  • error ignore — Mark an issue as ignored. Ignored issues do not reopen on new occurrences and do not generate alerts.
  • error reopen — Reopen a resolved or ignored issue, setting its status back to OPEN.
  • logs — Fetch logs from a deployed resource to investigate root causes of issues.