{"version":"2.1.224","anchor":"scheduled-tasks-can-resolve-loop-md-defaults-asynchronously","canonical_anchor":"scheduled-tasks-can-resolve-loop-md-defaults-asynchronously","heading":"Scheduled tasks can resolve loop.md defaults asynchronously","tier":"internal","area":"Scheduled Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/scheduled-tasks-can-resolve-loop-md-defaults-asynchronously","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Scheduled tasks can resolve `loop.md` defaults asynchronously\n\nScheduled tasks resolve loop.md content asynchronously and skip a fire rather than run unresolved.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- The skip is logged with the prefix \"[ScheduledTasks] loop.md v5 expansion failed; fire skipped: \" followed by the error.\n\n**Evidence**\n\n`[ScheduledTasks] loop.md v5 expansion failed; fire skipped: `\n\n- Area: Scheduled Tasks\n- Names: `loop.md`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}