{"version":"2.1.232","anchor":"durable-artifact-watch-gives-up-cleanly-when-it-cannot-get-a","canonical_anchor":"durable-artifact-watch-gives-up-cleanly-when-it-cannot-get-a","heading":"Durable artifact watch gives up cleanly when it cannot get a wake token","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/durable-artifact-watch-gives-up-cleanly-when-it-cannot-get-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Durable artifact watch gives up cleanly when it cannot get a wake token\n\nBackground artifact watching stops retrying once it is refused permission to wake your session.\n\n**What**\n\nThe background watch that wakes a session when a remote artifact changes now remembers when it was refused permission to wake, so later attempts stop immediately and report a distinct reason rather than retrying. The whole durable path is behind a feature check that reads remote configuration, and returns a skipped result with reason `flag_off` when that check fails, so the source does not say whether it is on for you.\n\n**Details**\n\n- Subscribe operations for a given watch are serialized, tracked in a pending set, and flushed on shutdown with a 10 second cap.\n- The keepalive ping for the live connection is now a named 25 second constant.\n\n**Evidence**\n\n`no_originator_latched`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}