← Documentation: Reliable Backup & Sync Execution Validation (Log-Driven)
The monitor distinguishes missing evidence from an unsuccessful execution. This helps you determine whether to investigate scheduling, the backup itself or an additional issue found in the log text.
The workflow lists the daily GCS prefix and reads the GitHub manifest. It uses each job's frequency and scheduling fields to decide which filenames are expected. Gmail: Alert missing Logs reports absent files.
A missing file can mean the job did not run or that upload, naming or date alignment failed. Check those conditions before interpreting it as a backup failure.
Available logs are parsed for lifecycle markers, return codes, error counts and warnings. A failed or incomplete result goes to Gmail: Alert Error. A present object alone does not establish success.
Code: Binary Text converts logs to text, AI Log Analyzer requests JSON, and Code: Ticket? evaluates severity and evidence. Qualifying findings go through Gmail: AI Alert Error.
The supplied delivery path is Gmail. GLPI ticket creation requires additional authenticated API nodes. AI processing sends log text to the configured provider, so review the data and usage costs.
Test multiple logs to confirm each is evaluated once and inspect overlap between alert types. Configure an independent n8n Error Workflow for failures such as authentication errors or an unreadable manifest. Verify routing with the scenarios in 04 · Testing, Troubleshooting & Security.