{"version":"2.1.248","anchor":"retry-table-for-cloud-session-startup-failures","canonical_anchor":"retry-table-for-cloud-session-startup-failures","heading":"Retry table for cloud session startup failures","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/retry-table-for-cloud-session-startup-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Retry table for cloud session startup failures\n\nCloud session startup failures are now classified as retryable or not.\n\n**What**\n\nCloud session startup failures now carry a reason and HTTP status, with a table saying which reasons are worth retrying. Epoch conflict, superseded by another worker, session not active and stale epoch are retryable; session not found, expired token and exhausted auth are not. A set of 401, 403, 404 and 429 sits alongside it. The error message itself already existed in the previous build, so what is new here is the classification table.\n\n**Evidence**\n\n`superseded_by_worker`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}