{"version":"2.1.242","anchor":"cloud-sessions-can-be-sent-hook-templates-before-registratio","canonical_anchor":"cloud-sessions-can-be-sent-hook-templates-before-registratio","heading":"Cloud sessions can be sent hook templates before registration","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/cloud-sessions-can-be-sent-hook-templates-before-registratio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Cloud sessions can be sent hook templates before registration\n\nCloud sessions can be handed a hook script up front, with a checksum so stale uploads get refused.\n\n**What**\n\nThe protocol between your machine and a cloud session gained an upload step that sends a hook script body (base64, at most 360,000 characters) with a SHA-256 the cloud side checks against its own table, optionally tagged with the worker generation so a stale upload is refused.\n\n**Details**\n\n- Registration replies now also carry which hook ids were ignored, which templates are held, and an \"away since\" timestamp set when this machine had been treated as absent after two forwarded hook runs went unanswered.\n- Documented refusals: hook forwarding disabled, hook forwarding not ready, stale worker generation, invalid upload, template refused.\n\n**Evidence**\n\n`@internal Success payload answering upload_device_hook_template.`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}