Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
In DevelopmentKind: in v2.1.246,
In DevelopmentSection of the release
A "not delivered to cloud session" error and its telemetry outcome exist with no constructor call.
What
A 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.
Details
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.
Evidence
Request was not delivered to the cloud session
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
