Oliver Kieselbach
1418eacfe9
Addresses Codex second-pass findings against commit bd3ec4e1:
#E (High) Deadline re-arm failure path was still catch+log-only. If
_scheduler.RehydrateFromSnapshot throws, DecisionState still claims the
deadline is active but the live scheduler never registered it — the same
phantom-deadline hang class already closed for live ScheduleDeadline /
CancelDeadline failures. The orchestrator now posts an
EffectInfrastructureFailure signal with the v1 payload contract through
the already-running ingress, so the reducer terminates the session
cleanly instead of deferring to the max-lifetime watchdog.
An IDeadlineScheduler? schedulerOverride constructor parameter was added
to EnrollmentOrchestrator so tests can drive the failure path with a
FakeDeadlineScheduler { ThrowOnSchedule = ... }.
#F (Medium) The inline EffectInfrastructureFailure signal synthesised by
SignalIngress.ProcessInlineAbortSignal only carried `reason` in the
payload and used a placeholder sourceOrigin. That broke the v1 contract
documented on DecisionSignalKind.EffectInfrastructureFailure + the
fixture (effect-infrastructure-failure-v1.json): { reason, failingEffect }
with sourceOrigin "effectrunner:critical:<EffectKind>" so forensic
consumers can distinguish ScheduleDeadline-vs-CancelDeadline failures.
ProcessItem now extracts the critical failure's EffectKind from
EffectRunResult.Failures (last non-transient entry) and threads it into
the synthetic signal's sourceOrigin, Evidence.Identifier and payload.
Suite-Baseline all green, 0 warnings:
DecisionCore 164/164, Agent.V2.Core 650/650, Functions 735/735.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Autopilot Monitor
Advanced monitoring and troubleshooting solution for Windows Autopilot deployments. Gain full visibility into every enrollment session with a detailed event timeline, fleet health dashboards, and session reporting. Define custom analysis rules to automatically detect issues and gather rules to collect targeted evidence. Retrieve diagnostics packages on demand, configure agent settings like auto-reboot behavior and automatic timezone adjustment — all managed centrally from the web dashboard.
Private Preview
Autopilot Monitor is currently running as a Private Preview. Visit autopilotmonitor.com to request access and learn more.
Overview
Autopilot Monitor provides real-time tracking, intelligent diagnostics, and automated troubleshooting for Windows Autopilot enrollment processes. It consists of:
- Bootstrap Script — PowerShell script deployed via Intune that starts monitoring early in the enrollment process
- Monitoring Agent — Lightweight .NET application that collects telemetry and evidence during enrollment
- Backend API — Azure Functions-based ingestion and processing pipeline
- Web Dashboard — Next.js application for real-time monitoring and fleet analytics
Architecture
For detailed information about the system architecture, components, and data flow, see Architecture Documentation.
Documentation
Full documentation is available at autopilotmonitor.com/docs
License
This project uses a split licensing model:
- MIT License — Agent (
src/Agent/) and Shared library (src/Shared/) — unrestricted use on end-user devices - AGPL-3.0 — Backend (
src/Backend/), Web Dashboard (src/Web/), and MCP Server (src/McpServer/) — server-side components remain open source
See LICENSE for full details.