{"version":"2.1.242","anchor":"scheduled-task-runs-carry-a-task-and-a-per-run-identifier","canonical_anchor":"scheduled-task-runs-carry-a-task-and-a-per-run-identifier","heading":"Scheduled task runs carry a task and a per-run identifier","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/scheduled-task-runs-carry-a-task-and-a-per-run-identifier","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Scheduled task runs carry a task and a per-run identifier\n\nEach scheduled task run now carries its own id, so a run can be traced back to its schedule.\n\n**What**\n\nEach scheduled-task firing now passes the task and a fresh per-run id through to the query it starts, so a run can be tied back to the schedule that triggered it.\n\n**Details**\n\n- The `\/loop` branch no longer consults the separate loop-enabled check before rewriting the queue, and the \"Claude resuming \/loop wakeup\" message variant is gone from this path; the scheduled-task variant remains.\n\n**Evidence**\n\n`Running scheduled task (`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}