Scheduled tasks resolve loop.md content asynchronously and skip a fire rather than run unresolved.
What's wrong with this entry?
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.
- The skip is logged with the prefix "[ScheduledTasks] loop.md v5 expansion failed; fire skipped: " followed by the error.
[ScheduledTasks] loop.md v5 expansion failed; fire skipped:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
Scheduled loops get a usage table
Both mention loop scheduled
-
v2.1.238
Scheduled runs are told the notification is how the result reaches you
Both mention scheduled
-
v2.1.246
The interactive session was split into controllers and stores
Both mention loop