{"version":"2.1.265","anchor":"new-durable-declined-live-subscription-state-gets-its-own","canonical_anchor":"new-durable-declined-live-subscription-state-gets-its-own","heading":"New 'durable_declined' live-subscription state gets its own message","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-durable-declined-live-subscription-state-gets-its-own","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New 'durable_declined' live-subscription state gets its own message\n\nA new durable_declined live-subscription state now shows its own distinct message\n\n**What**\n\nWhen an artifact's live subscription (the mechanism that keeps a published artifact updating live) has the state `durable_declined`, Claude Code now shows a distinct message for it instead of falling back to a generic message used for other states.\n\n**Why**\n\nThis gives users clearer, more specific feedback about why a live subscription isn't active in this particular case, building on the live-subscription support for artifacts published from a type.\n\n- Area: Artifacts\n- Names: `durable_declined`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}