{"version":"2.1.246","anchor":"an-undelivered-request-error-type-exists-but-nothing-constru","canonical_anchor":"an-undelivered-request-error-type-exists-but-nothing-constru","heading":"An undelivered-request error type exists but nothing constructs it","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/an-undelivered-request-error-type-exists-but-nothing-constru","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### An undelivered-request error type exists but nothing constructs it\n\nAn error for requests never delivered to a cloud session exists but nothing creates it yet.\n\n**What**\n\nA new error carrying the fixed message \"Request was not delivered to the cloud session\" sits beside the existing control-request timeout error, and the classifier maps it to a telemetry outcome of \"not_delivered\" alongside aborted, timeout, disconnected, not_connected and server_error.\n\n**Details**\n\n- No code in the control-request module creates one, so the outcome cannot currently be reported. Other occurrences of \"not_delivered\" in the bundle belong to the unrelated directory-sync result kinds.\n\n**Evidence**\n\n`Request was not delivered to the cloud session`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}