{"version":"2.1.234","anchor":"publishing-tells-relay-failures-apart-from-real-service-answ","canonical_anchor":"publishing-tells-relay-failures-apart-from-real-service-answ","heading":"Publishing tells relay failures apart from real service answers","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/publishing-tells-relay-failures-apart-from-real-service-answ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Publishing tells relay failures apart from real service answers\n\nA publish answer that didn't come from the artifact service is reported as a relay error with its status.\n\n**What**\n\nWhen a publish, deploy or upload answer did not actually come from the artifact service, it is now reported as a relay error carrying the HTTP status and a message saying the publish was not completed, instead of being parsed as if it were a deploy result.\n\n**Details**\n\n- Responses carry a marker recording whether they came from the artifact service itself.\n- New telemetry reasons: `relay_error`, `upload_relay_error`, `prepare_upload_relay_error`.\n- The related HTTP call sites dropped their per-call host, auth and status-validation options.\n\n**Evidence**\n\n`prepare_upload_relay_error`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}