# Monitoring Workflows This page showcases the various monitoring workflows and processes used in Uptime Watcher. ## Site Monitoring Lifecycle This flowchart shows the complete lifecycle of monitoring a site from creation to deletion:## Monitor Type Decision Tree This diagram helps users choose the appropriate monitor type for their needs:## Error Handling and Recovery Flow This diagram shows how the system handles errors and implements recovery strategies::::note Partial failure states are captured in the monitoring summaries emitted by Electron and surfaced to the renderer as lifecycle telemetry. The current UI surfaces the aggregate counts via notifications and logs rather than a dedicated "partial failure" badge. ::: ## Data Flow and Synchronization Strategy The current architecture centers on a single standardized cache inside Electron that feeds both IPC responses and broadcast events, while the renderer relies on typed services plus automatic full-sync recovery when payload validation fails:During normal operation the renderer requests an initial snapshot through `StateSyncService.requestFullSync()`, then stays synchronized through `state-sync-event` broadcasts. When an invalid payload is detected, the new automatic recovery flow triggers a guarded full sync and replays a synthetic bulk update so stores never diverge from Electron state. ## Scheduled Monitor Check Lifecycle This sequence illustrates how a scheduled monitor run traverses the enhanced monitoring stack, from the interval scheduler, through operation correlation, to the renderer update and desktop notifications.--- These workflow diagrams provide detailed insights into how Uptime Watcher processes monitoring tasks, handles errors, and manages data flow throughout the system.