{"version":"2.1.232","anchor":"artifact-wake-subscriptions-explain-a-missing-human-originat","canonical_anchor":"artifact-wake-subscriptions-explain-a-missing-human-originat","heading":"Artifact wake subscriptions explain a missing human originator","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/artifact-wake-subscriptions-explain-a-missing-human-originat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Artifact wake subscriptions explain a missing human originator\n\nArtifact wake subscriptions now explain when a session has no human owner to wake.\n\n**What**\n\nThe reasons an artifact wake subscription can fail moved into a lookup table and gained a new case, `no_originator`, for sessions with no linked human owner. It explains that such a session cannot hold wake subscriptions, that retrying deliberately re-checks, and that automatic retries are answered locally.\n\n**Details**\n\n- A latched form of the same condition is reported in telemetry as `no_originator_latched`.\n- Sits behind the same artifact gating as the rest of the artifact wake feature.\n\n**Evidence**\n\n`no_originator`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}