I said my automation never ran. Five file timestamps proved me wrong.

Описание и применение

Автоматизация продолжала работать, но неверный статусный файл вводил в заблуждение. Добавление проверки временных меток файлов и логов предотвратило ложные выводы.

Задача

Assuming a scheduled job had stopped because a state file was stale, leading to unnecessary debugging and client communication.

Результат

Automation ran correctly; the stale state file misled the operator. Implementing multiple evidence checks prevented unnecessary debugging.

Рабочий процесс

• 1. Check state file timestamp. 2. Inspect queue file modification times. 3. Verify log file existence for the date. 4. Compare status field with other evidence. 5. Update monitoring to require all three evidence classes before flagging failure.
• 6. Adjust job to write status only after successful completion.
• 7. Investigate and fix quota truncation issue.

Доказательства

I now require three evidence classes before concluding a job did not run. Queue file modification times. Whether a log file exists for that date. And only then the status field.

Источник

The automation had run. Five times. It just never wrote back the status field I was using as my only signal.

Источник

If a job is interrupted, or crashes after doing its real work, or writes status only on certain paths, the status field lies.

Источник