The error reopen command sets a previously resolved or ignored issue back to OPEN status. It is most useful for ignored issues, which do not auto-reopen on new occurrences — manual reopening is required to restore them to active tracking. You can also reopen a resolved issue before waiting for the next automatic reopen on error recurrence, or when a teammate resolved an issue prematurely. Once reopened, the issue appears in error list with OPEN status.
Usage
The error reopen command takes one required argument, the issue ID, to identify the issue to reopen. It requires a valid Stacktape API key (configured via stacktape login).
On success, the command calls the Stacktape API and prints Issue <issueId> reopened.
Examples
Reopen an issue by its ID:
Reopen using the short alias:
Reopen in agent mode for programmatic consumption:
Arguments reference
The table below lists all accepted flags for error reopen.
stacktape error reopen <issue-id>CLI options--issue-id (positional 1)requiredstringIssue ID
The ID of the issue to act on.
-h, --helpstringShow Help
If provided, the command will not execute and will instead print help information.
--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.
--quietbooleanQuiet
Hide progress, banners, success messages and hints. Command output, warnings and errors are still printed.
Related commands
The issue lifecycle commands — list, resolve, ignore, and reopen — let you triage runtime issues from the CLI.
error list— List detected runtime issues with their error message, type, function name, project/stage, occurrence count, and status.error resolve— Mark an issue as resolved. It will reopen automatically if the same error occurs again.error ignore— Mark an issue as ignored. Ignored issues do not reopen on new occurrences.