{"version":"2.1.248","anchor":"worker-check-in-re-arms-when-its-interval-changes-and-asks-f","canonical_anchor":"worker-check-in-re-arms-when-its-interval-changes-and-asks-f","heading":"Worker check-in re-arms when its interval changes, and asks for a time estimate","tier":"notice","area":"Background Work","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/worker-check-in-re-arms-when-its-interval-changes-and-asks-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Worker check-in re-arms when its interval changes, and asks for a time estimate\n\nThe dispatched-work reminder now follows interval changes and asks Claude for a time estimate.\n\n**What**\n\nThe reminder that fires while dispatched work is still running now checks the current interval on each tick and re-arms itself if it has changed, instead of quietly running on the old schedule. Its wording also changed: it is summarised as \"Worker check-in: dispatched work still running\" and now asks the model to tell you how long it expects the work to take, rather than to post a status.\n\n**Details**\n\n- Re-arming carries over the same task registry and known worker set.\n- A new helper registers an additional worker into a check-in that is already armed, instead of starting a second one.\n\n**Evidence**\n\n`Worker check-in: dispatched work still running`\n\n- Area: Background Work\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}