{"version":"2.1.251","anchor":"cloud-sessions-report-why-they-failed-to-start","canonical_anchor":"cloud-sessions-report-why-they-failed-to-start","heading":"Cloud sessions report why they failed to start","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/cloud-sessions-report-why-they-failed-to-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Cloud sessions report why they failed to start\n\nA cloud session that failed to start now shows the actual reason instead of a generic error.\n\n**What**\n\nWhen a cloud session is polled, for example under `--print`, a recorded startup failure is now raised as that specific error instead of the generic archived-or-errored response, so you see the actual reason the session never came up.\n\n**Details**\n\n- gated on `tengu_linear_brook`, which defaults to on in this build\n- with the flag off, polling falls back to the previous generic result\n\n**Evidence**\n\n`if (n.startupFailure && FNt()) throw T(n.startupFailure);`\n\n- Flag `tengu_linear_brook`: Not enough to say (read for one account on one subscription tier against v2.1.251; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Cloud Sessions\n- Names: `--print`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}