{"version":"2.1.227","anchor":"workshop-authoring-progress-failures-now-report-telemetry","canonical_anchor":"workshop-authoring-progress-failures-now-report-telemetry","heading":"Workshop authoring-progress failures now report telemetry","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/workshop-authoring-progress-failures-now-report-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Workshop authoring-progress failures now report telemetry\n\nWorkshop authoring-progress failures now report once per session instead of only hitting the log.\n\n**What**\n\nErrors in the workshop authoring-progress hooks were previously only written to the log. They now also emit a telemetry event, once per session at most, and a separate one when the module cannot be loaded at all.\n\n**Details**\n\n- The keys are `hook_failed` and `module_load_failed` under `workshop_authoring_progress`; a `failureReported` flag stops repeat reports.\n- The lazy loader was restructured into a class whose reset can swap the require function, a test seam.\n\n**Evidence**\n\n`workshop authoring-progress module failed to load`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}