{"version":"2.1.238","anchor":"durable-wake-subscriptions-now-say-why-they-failed","canonical_anchor":"durable-wake-subscriptions-now-say-why-they-failed","heading":"Durable wake subscriptions now say why they failed","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/durable-wake-subscriptions-now-say-why-they-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Durable wake subscriptions now say why they failed\n\nFailed wake subscriptions now show a reason in artifact `status` plus a one-off notification.\n\n**What**\n\nArming a durable wake subscription is tracked while in flight and settles to registered, stopped, pending or unregistered. Failures show up as a `durable_wake` line in the artifact `status` output and as a one-shot notification, with a reason instead of silence.\n\n**Details**\n\n- New reasons: `no_wake_minter`, `tool_not_offered`, `org_not_enabled`, `flag_off`, `aborted` and `watch_trigger_release_failed`.\n- The organization case says plainly that retrying will not help while that holds.\n- The gating on whether a subscription is attempted at all is unchanged.\n\n**Evidence**\n\n`Wake subscriptions are not enabled for the user's organization, so none was registered; retrying will not help while that holds.`\n\n- Area: Artifacts\n- Names: `status`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 3\/5"}