{"version":"2.1.247","anchor":"cloud-event-posts-accept-a-per-call-timeout","canonical_anchor":"cloud-event-posts-accept-a-per-call-timeout","heading":"Cloud event posts accept a per-call timeout","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/cloud-event-posts-accept-a-per-call-timeout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Cloud event posts accept a per-call timeout\n\nCloud event posts can now be given a time limit, so control replies cannot block forever.\n\n**What**\n\nThe cloud sessions client's event post takes an options object and threads a timeout through every attempt, including the retry after a 401 refresh and the retry after re-enrolling an untrusted device; control responses forward the same options. Failures were already classified as timeout versus network, so callers can now bound how long a control response blocks.\n\n**Evidence**\n\n`async postEvent(e, t = {}) {`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}