Exercise 1: A Backup Task That Simply Never Ran — Possible Solution
====================================================================

THE MOST LIKELY CAUSE
------------------------------
Per this chapter's own warn-box, "a condition like 'start only if the
computer is on AC power' causes the task to be skipped entirely on a
laptop running on battery, with no failure logged, since the task was
never actually started in the first place." On a laptop specifically,
the most likely explanation is that the backup task has an "only run on
AC power" condition set, and the laptop was running on battery power
(not plugged in) when the scheduled trigger time arrived overnight.

WHY THERE'S NO ERROR TO SEE
------------------------------
Per this chapter, "'it never ran' and 'it ran and failed' look
identical at a glance in the task's overview." Because the condition
prevented the task from ever starting at all, there's no failure to
report - a failure implies the task attempted to run and encountered a
problem, whereas a skipped condition means the task was never launched
in the first place. Windows has nothing to log as an error, since
nothing went wrong from Windows's own point of view - the task simply
correctly followed its own configured condition.

WHAT TO CHECK
------------------------------
Per this chapter, "only the History tab (once enabled) distinguishes
them." Checking the task's History tab (assuming it was enabled in
advance, per this chapter's own tip-box) would show whether the task
was triggered at all overnight, or skipped due to the AC-power
condition. Separately, checking the task's own Conditions tab in its
properties would confirm whether an "only on AC power" condition is
actually configured, which is the direct fix if found - either removing
that condition or ensuring the laptop stays plugged in during the
scheduled window.

WHY THIS MATTERS FOR HOW THE PROBLEM SHOULD BE FRAMED
------------------------------
This isn't a "the task is broken" problem to fix by reconfiguring the
backup action itself - the task, action, and trigger may all be
perfectly correctly configured. The real issue is a condition silently
preventing the task from ever starting under a specific, easily
overlooked circumstance (running on battery), which is a configuration
question, not a failure to debug.

WHY THIS WORKS AS AN ANSWER
------------------------------
It identifies the AC-power condition as the specific likely cause using
this chapter's own warn-box, explains precisely why no error appears in
this scenario, and names the concrete checks (History tab, Conditions
tab) that would confirm and resolve it.