{"version":"2.1.235","anchor":"artifact-durable-watch-failures-are-logged-with-the-servers","canonical_anchor":"artifact-durable-watch-failures-are-logged-with-the-servers","heading":"Artifact durable-watch failures are logged with the server's own message, and relayed subscribes are tagged","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/artifact-durable-watch-failures-are-logged-with-the-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Artifact durable-watch failures are logged with the server's own message, and relayed subscribes are tagged\n\nArtifact durable-watch failure logs now include the server's message and flag whether the subscribe went through a relay\n\nSubscribe telemetry for artifact durable watches now carries a `{relay: true}` marker when the request was made over the relay route. Expected failures are logged at debug level while unexpected ones still warn, and the log line now includes the server's own failure message, mapped from server codes to closed states.\n\nA redaction pass scrubs sensitive words and URLs from these messages before they are reported.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}