A scheduled audit did not run
Diagnose skipped or failed scheduled audits using exit codes, the scheduled-audits log, Windows Task Scheduler and Slack failure messages.
The task did not run at all
Scheduled tasks run only while you are logged in. If the computer was off, asleep or signed out at the scheduled time, the run is skipped. Open Schedule audits.bat and choose to run everything now to confirm the setup still works.
Check the log
Every scheduled run writes to:
%LOCALAPPDATA%\SiteAuditor\SiteAuditor\logs\scheduled-audits.logExit codes
| Code | Meaning | What to check |
|---|---|---|
| 0 | Finished | Nothing to fix |
| 1 | An audit failed | The log, and the failure message in Slack |
| 2 | No sites or bad arguments | scheduled_sites.txt has at least one URL per line |
| 3 | Audits finished, Slack or Linear failed | Slack or Linear not working |
The audit ran but was not posted
With Only when something gets worse selected, nothing is posted unless new critical issue URLs appeared or site health dropped 5 points or more. Switch to after every audit to confirm messages arrive.
Secrets not found in scheduled runs
Scheduled runs read Slack, Linear and AI keys from Windows Credential Manager. If the app was started with python run_app.py without the keyring package, keys may have been saved to the fallback file instead. Run python -m pip install keyring and save the connections again.
Applies to SiteAud!tLint 0.4.0 and later. Current version 0.7.1.