Repeat useful work

A scheduled task failed or its result did not arrive

A missing report can mean the job did not run, the analysis failed, or the result was produced but not delivered. Check which happened before repeating the work.

Start with the schedule

Open Scheduled Tasks in the correct workspace. Find the job and check whether it is enabled. A disabled job is paused; that alone is not a failed run.

The card shows the schedule as a cron expression with its timezone, for example 0 6 * * 1 (New_York), meaning 6:00 every Monday, New York time. It does not show a next-run time. If you cannot read the expression, ask Winston or Support to confirm the saved configuration. Do not rely on an old chat promise when the saved task disagrees.

Let Overview tell you

Scheduled task failures is a check in Your checks (any Overview card's menu, or Choose what on the email banner). It is off until you switch it on. With Show on, a failed job becomes an Overview card that says how bad it is; with Email on, it reaches your inbox too.

The card's button is Fix it. It opens a panel with each job's recent runs; a failed run expands to its own error, and an unclassified failure shows the raw error with no recommendation. Ask Winston fills the composer with the job name, schedule and every recent outcome, so Winston can see what changed. Nothing is sent until you send it, and nothing is retried from that panel.

Locate the failure

What you find	Next step
No saved job	The page reads "No scheduled tasks. Ask Winston in chat to create one." Confirm whether setup completed; do not assume the request created it.
Disabled job	Confirm why it was paused before enabling it.
Enabled, expected time passed	Ask for the last attempted run, status and error.
Connection or missing-data error	Check the source with an admin before retrying. See Data coverage.
Credit-related failure	Check Billing and Usage and resolve the balance issue before retrying. See Account and access.
Result exists in Chat or Library but nothing arrived externally	Check the delivery destination, authorization and any delivery error. The analysis may not need to run again.
Task says completed but destination is empty	Verify delivery separately; completed analysis is not proof that a message arrived.

Retry without duplicating work

Before rerunning, check whether the previous attempt already published a file, sent a message or changed a record. Ask to retry only the failed step when supported. If it is unclear whether an external action happened, confirm at the destination or contact Support first.

If you need to stop future attempts, pause the saved task. Confirm separately whether an already-running attempt has stopped.

What to send Support

Include the workspace, task name, expected run time and timezone, last successful run if known, error text, intended destination and a link to the relevant conversation or output. Include the observed state rather than only "nothing arrived."

A failure only reaches you if the Scheduled task failures check is switched on under Your checks, and it reports a failed run, not a failed delivery. Use Scheduled Tasks and the result destination to verify execution and delivery; the absence of a card is not proof of success.

Setting up and changing recurring work: Automation.