The task that trusted the PATH

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

Задачи планировщика Windows иногда терпят беззвучные ошибки из‑за разницы в переменной PATH. Указав абсолютный путь к интерпретатору и применив правило проверки из трёх доказательств, можно гарантировать успешное выполнение.

Задача

Scheduled tasks sometimes fail silently because the task scheduler runs in a sparse environment where the PATH variable differs from interactive shells, causing commands like "python" to be unresolved.

Результат

All scheduled tasks now reference absolute paths, eliminating silent failures. The three‑proof acceptance rule provides a reliable receipt of task execution, improving auditability and reliability.

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

• 1. Run a retro-audit of all scheduled tasks to identify those in state "Ready". 2. Inspect the Execute field of each task; if it contains only a command name (e.g., "python"), note it. 3. Verify the task’s environment: the scheduler’s PATH is sparse compared to interactive shells. 4. Resolve the full path to the interpreter (e.g., C:\Python39\python.exe) and update the task’s Execute field. 5. Re‑run the task manually to confirm success. 6. Implement an acceptance rule: after a deliberate Start call, check that Start returned, LastRunTime is today, and LastTaskResult is 0. 7. Apply the rule to all tasks; tasks that pass are marked accepted, those that fail are fixed and re‑tested. 8. Document the process and maintain the rule for future audits.

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

The bug had passed every eyeball check since this morning. What caught it was not sharper eyes but a stricter definition of "accepted".

Источник

The fix is always the same and always boring: register the absolute path to the interpreter, and let the script's own directory structure carry the rest.

Источник