The error ignore command marks a runtime issue as ignored. Ignored issues will not reopen on new occurrences and will not generate alerts. You can reopen an ignored issue at any time with error reopen. Use this for errors you've reviewed and decided are not actionable, rather than error resolve which will automatically reopen if the same error recurs.
Usage
You can find issue IDs by running error list. This command requires a Stacktape API key — run login first if this machine is not yet authenticated.
Flags Reference
stacktape error ignore <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.
Examples
Ignore a specific issue by its ID:
Use agent mode for scripted or CI workflows where you need structured JSON output:
When to Ignore vs Resolve
Use error ignore for errors you've reviewed and determined are not actionable — for example, recurring runtime errors that you've investigated and confirmed don't require a code fix. Ignored issues stay silent until you explicitly reopen them with error reopen.
Use error resolve when you've fixed the root cause. A resolved issue will automatically reopen if the same error recurs, keeping you informed of regressions.
Related Commands
error list— list detected runtime issues with filtering by status, project, or stageerror resolve— mark an issue as resolved (will reopen on recurrence)error reopen— reopen a previously resolved or ignored issue