{"version":"2.1.242","anchor":"answers-sent-back-to-a-cloud-session-are-retried-and-losses-","canonical_anchor":"answers-sent-back-to-a-cloud-session-are-retried-and-losses-","heading":"Answers sent back to a cloud session are retried, and losses are reported","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/answers-sent-back-to-a-cloud-session-are-retried-and-losses-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Answers sent back to a cloud session are retried, and losses are reported\n\nYour answers to cloud-session prompts are retried with backoff, and you are told if one is lost.\n\n**What**\n\nWhen you answer a permission prompt, dialog or hook for a session running in the cloud, the answer is now kept if it cannot be delivered, re-posted with a 1s, 5s, 15s and 45s backoff, and re-sent on reconnect. If it is finally lost you get a message naming which kind of answer went missing and suggesting you interrupt and retry.\n\n**Details**\n\n- Retention is behind the manager setting `keepUndeliveredResponses`; without it an answer is posted once and forgotten.\n- Hook answers have a separate \"overtaken\" path for when the cloud worker cancelled the request before the answer arrived.\n- Also here: hook callbacks forwarded from the cloud and answered on this machine, send gates that can hold or withdraw a queued message, and a withheld first prompt that is retried and reported through `tengu_home_seed_prompt_resequenced`.\n\n**Evidence**\n\n`A permission answer you gave could not be delivered to the cloud session, which may still be waiting for it. If the session looks stuck, interrupt it and retry.`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}