Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.232,
In DevelopmentSection of the release
What
The 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.
Details
A latched form of the same condition is reported in telemetry as no_originator_latched.
Sits behind the same artifact gating as the rest of the artifact wake feature.
Evidence
no_originator
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
