“I did not receive a report” can describe several failures: a routine never started, it started but could not read a source, or it completed with nowhere useful to put the result. Diagnose those separately.
Check the saved schedule
Inspect what was actually saved, including the time zone and whether the routine is active. A scheduled routine does not necessarily execute immediately after creation; the official guide distinguishes the next scheduled run from a manual test.
Write down the expected time and the account's time zone before changing anything. This prevents confusing a schedule error with a delayed notification.
Look for a run before assuming a failure
Inspect the available run history and conversation. Is there a start time, a returned report, a missing-input question, or an approval request? An output failure is different from a trigger failure.
If the workflow can validly find nothing, define how that appears. “No new items” and “source unavailable” should never be silently treated as the same result.
Test the same work once
Request a one-time run using the same inputs. Preserve any error and the source that failed. If the manual task works but scheduled runs do not, keep that observation; it narrows the problem without proving a particular cause.
Run this routine's task once using its saved inputs. Tell me which source was checked, the time window used, and where the result was saved. If it cannot finish, report the exact blocked step. Do not create a duplicate routine.Check access and pending actions
Confirm that the connected service is still signed in, required input still exists, and the account has usable allowance. Review pending approval cards. Do not assume granting more permissions will fix a scheduling problem.
Check official status and record evidence
Use the linked official status and troubleshooting resources. A past community incident does not establish that the service is down now. When seeking support, include the expected run time with time zone, actual history, manual-test result, app version, and any error text.
Recreating a routine immediately can remove useful evidence and produce duplicates. Fix a confirmed configuration problem, then test once. Our routine design guide explains how to make future failures easier to inspect.