Use a routine's Run history to check what happened, find the reported problem, and decide whether another run is appropriate. Start with the saved configuration and the latest result so you do not repeat work that has already completed.
If you have not built the workflow yet, start with Creating a recurring routine.
Check the routine before testing
Open Routines and select the routine you want to inspect. Confirm its name and purpose, then review:
- Steps: check the selected data sources, jobs, and scripts. On a built-in routine, expand the step chain or choose Edit steps when you need to inspect its configuration.
- Delivery: check Notifies and your Notify me subscription. A displayed default destination can be used when you run the routine.
- Output: use Read it in when shown, or confirm where the selected operation writes its result.
- Schedule: check Runs, the timezone, and whether the routine is on or off.
Resolve visible setup notices first. A job that uses AI needs a working provider; a routine that requires notifications needs a valid destination. Editing or running a routine also requires the appropriate feature access.
Save any intended changes with Save changes before testing. Apply schedule only updates the form until you save the routine. If the routine is already on, saving changes can update the configuration used by future scheduled runs. Turn it off first if you want to work through a correction without future scheduled runs starting.
Run one deliberate test
Run now performs real work. It can call AI, change data, create content, or send notifications according to the routine's configured operations. AI work can add to your usage and costs. Review those effects before starting.
- Check the latest Run history and the output destination for work that has already completed.
- Confirm that the saved steps and recipients are the ones you intend to test.
- Select Run now once.
- Read the response. A message saying the routine was queued means the request was accepted; it does not mean execution succeeded.
- Follow the new entry in Run history, then inspect the resulting output or notification.
You can run a saved draft manually while its recurring schedule is off. A manual run does not turn recurring runs on.
Do not click Run now repeatedly while waiting. If the page reports a request error or loses its connection, reopen the routine and check its history before trying again. The first request may already have been accepted.
A queued manual run uses the routine steps and settings saved when it was queued. Editing the routine afterward does not replace that queued configuration. Stopping future scheduled runs is not a way to undo work already requested.
Read the run outcome
In Run history, find the relevant time and choose Show details on that run. Use Show more runs if the entry you need is farther down the available history.
- Succeeded: the run completed. Read what it changed or produced, and check that the result meets your goal.
- Failed: the run reported an error. Read the recorded reason and any step details before correcting the routine or retrying.
- Skipped: the run did not execute as expected. Read the reason; for example, scheduled work may be skipped after the routine was stopped or its approved configuration changed.
- Running: execution is still in progress. Wait for a later outcome before starting another run.
- Retry scheduled: another attempt is planned. Check the attempt count and next-attempt time when shown before adding a manual run.
A skipped step inside an otherwise completed run is different from the whole run being skipped. A branch condition can intentionally leave a step unused; check the condition and whether the expected path produced the result.
Expanded details can show the step name, type, status, duration, reason, and a preview of its output. These fields depend on what the run recorded. An output preview may be shortened, so use the actual destination to inspect the complete result.
If the entry says no step-by-step detail was recorded, use its overall reason and check the output destination. Missing detail does not prove that no work occurred.
Resolve the reported problem
Use the error to choose a focused correction:
- No job selected, missing job, or disabled job: check the Job selection and ask the administrator to restore or enable the intended job. Do not substitute an unrelated operation just to make the step run.
- No data sources selected or a source failed to load: check the Data call step and its source selection. If a selected service is unavailable, resolve that connection before another run.
- Missing script or a script error: check the selected Script and give its maintainer the reported step and error. Review the correction before running it again.
- Provider or model error: check the selected job's provider and model setup. For a spending-limit error, review usage and the configured limit before choosing whether to increase it.
- Nowhere to deliver or an unavailable notification channel: review Delivery and choose a connected destination or a valid personal subscription. Check the actual recipients before saving.
- Unsaved changes: save the intended configuration before using Run now or turning the routine on.
For a built-in routine, use Edit steps when a step selection needs correction. For your own routine, the step editor is already shown. After changing a source, job, or script, review the sequence again: later steps may depend on the earlier output.
If the error identifies a removed or outdated step type, ask the administrator to replace it with a supported operation. Repeating the same run will not repair the configuration.
When a scheduled run does not appear
Check that the routine is On and that its saved Runs schedule is correct. A saved draft remains off until you turn it on.
Review the timezone and the next-run time when shown. A weekly run needs the intended weekday; a monthly date after the 28th is skipped in a month without that date. Reopen Change beside Runs if you need to inspect the schedule, and save only if you intend to change it.
If the site was unavailable, check Catch up missed runs after downtime. Do not assume every missed run will automatically be replayed. Decide whether late work is still useful before enabling catch-up or requesting a manual run.
If a scheduled entry is Skipped, read its reason. A stopped routine or a configuration that needs approval can prevent scheduled execution. Review and save the intended setup, then turn the routine on when you are ready to resume.
When the run succeeds but the result is wrong or missing
Succeeded does not guarantee that the content is accurate, that it was published, or that every recipient received a notification. Check what the selected operation was meant to do.
For an inaccurate summary, inspect the selected sources, reporting period, step order, and the job's saved instructions. Correct those inputs before asking the same workflow to produce another answer.
For missing output, read the run summary and step previews, then inspect Read it in when available or the operation's destination. A notification may contain only a short update rather than the complete result.
For missing notifications, check Notifies, the connected channel, and your Notify me subscription. Turning your subscription off does not stop the routine or other recipients' notifications. Ask an administrator to inspect delivery if the destination is correct but nothing arrived; rerunning the entire workflow can duplicate its other effects.
Retry and verify the correction
- Check what the earlier run already created, changed, or sent.
- Make the smallest correction that addresses the reported problem, then save it.
- Check for a run already in progress or a scheduled retry.
- If another manual run is appropriate, select Run now once and inspect the new result.
- Confirm the intended output and delivery. If you paused the routine, turn it on only when you want future scheduled runs to resume.
For an unresolved issue, ask for help with the routine name, run time and timezone, outcome, affected step, visible error, and whether it was a manual or scheduled run. Mention any work that already completed. Share only the output or screenshot needed to explain the problem, with credentials and unrelated private information removed.