{"version":"2.1.288","anchor":"unawaited-plugin-promise-rejection-message-factored-out-and","canonical_anchor":"unawaited-plugin-promise-rejection-message-factored-out-and","heading":"The error for a plugin's unhandled failed task may appear in more situations","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/unawaited-plugin-promise-rejection-message-factored-out-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### The error for a plugin's unhandled failed task may appear in more situations\n\nClaude Code's error for a failed plugin task the plugin never waited on is now shared and can be reported from more places\n\n**Unclear.** It is not clear whether the additional places that produce this message are actually reached.\n\n**What**\n\nA plugin, an add-on that extends Claude Code, can start a task and not wait for its result. When such a task fails, Claude Code reports it with a message beginning \"hooks (same thread): a promise a plugin did not await rejected:\". That message is now built in one shared place and can be produced from more kinds of failure, not only the single case it covered before.\n\n**Why**\n\nThis is a small change for consistency, so failures of this kind are described the same way wherever they are caught.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}