{"version":"2.1.292","anchor":"loop-wakeup-scheduling-tracks-tooluseid-and-chain-start","canonical_anchor":"loop-wakeup-scheduling-tracks-tooluseid-and-chain-start","heading":"\/loop wake-ups record when the chain started and what triggered them","tier":"internal","area":"Loop","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/loop-wakeup-scheduling-tracks-tooluseid-and-chain-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### `\/loop` wake-ups record when the chain started and what triggered them\n\nScheduling the next \/loop wake-up now records when the loop chain started, whether a keepalive triggered it, and which tool call scheduled it\n\n**What**\n\n`\/loop` runs a task repeatedly, waking up at intervals. Scheduling the next wake-up has been reworked. It now records:\n\n- when the chain of wake-ups started\n\n- whether the wake-up came from a keepalive\n\n- which tool call scheduled it\n\nBefore, the wake-up was built directly as a timed schedule entry without this information.\n\n**Why**\n\nThis is an internal rework of how `\/loop` schedules itself. It does not show a visible change in how loops behave.\n\n- Area: Loop\n- Names: `\/loop`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}