Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Scheduled TasksArea: what it touches
In DevelopmentKind: in v2.1.224,
In DevelopmentSection of the release
What
When a storage store is available, the scheduled-task fire path queues fires one after another and awaits an asynchronous resolution of loop.md default content. If that resolution fails, the fire is logged and skipped rather than running with unresolved content. Without a store, the existing synchronous resolution runs.
Details
The skip is logged with the prefix "[ScheduledTasks] loop.md v5 expansion failed; fire skipped: " followed by the error.
Evidence
[ScheduledTasks] loop.md v5 expansion failed; fire skipped:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
