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.

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

What you findNext step
No saved jobThe page reads "No scheduled tasks. Ask Winston in chat to create one." Confirm whether setup completed; do not assume the request created it.
Disabled jobConfirm why it was paused before enabling it.
Enabled, expected time passedAsk for the last attempted run, status and error.
Connection or missing-data errorCheck the source with an admin before retrying. See Data coverage.
Credit-related failureCheck Billing and Usage and resolve the balance issue before retrying. See Account and access.
Result exists in Chat or Library but nothing arrived externallyCheck the delivery destination, authorization and any delivery error. The analysis may not need to run again.
Task says completed but destination is emptyVerify 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."

Do not assume every scheduled-task failure will appear as an Overview card. Use Scheduled Tasks and the result destination to verify execution and delivery. If your workspace exposes a failure alert, follow its details; its absence is not proof of success.

Setting up and changing recurring work: Automation.