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.
Check the cadence, timezone and delivery setting. If the next run or a readable schedule is not available, ask Winston or Support to confirm the saved configuration. Do not rely on an old chat promise when the saved task disagrees.
Locate the failure
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."
Setting up and changing recurring work: Automation.