Schedule runs and check for failures

In one line

Schedule runs and check for failures
Not just when it runs, but where it runs and who checks it.

The big picture

Checking time, time zone, and data location when scheduling — Click the picture to see it larger.

Follow along

Only schedule tasks that already work by hand

Whether scheduling is available depends on your account and workspace. First run the prompt by hand and check that the input and results are right. This guide shows how to schedule, but doesn’t create a real schedule.

Check four things about the schedule

1. Decide the task and where results go

Write down the scope, for example “Draft a weekly summary of this specific material.” Include where you’ll review the results and how it should tell you if the material is missing.

2. Set how often and the time zone

For every Monday at 9 a.m., also give a time zone like America/New_York. Check whether it runs once or repeats. After asking for the schedule in the chat, review the saved settings.

3. Check the first run under Scheduled

On the scheduled tasks screen available to your account, check the saved task and its run history. Look at the status and errors so a failed run with no results isn’t mistaken for a normal one.

4. Also learn how to stop or change it

If the schedule or input changes, edit or pause the scheduled task. Also check that the same task wasn’t created twice.

Prompts you can copy

Review the settings before scheduling

Review this draft schedule for a repeating task. Don't create the schedule yet. Task: [a task already checked by hand] When: [day and time], time zone [e.g. America/New_York] Input location: [local folder / upload / connected service] Where to review results: [where I'll check] Check whether this setup supports it, and the conditions for data access and my computer being on. If the data is missing or the run fails, report it instead of treating it as a success. Also explain how to prevent double runs and how to pause it.

Check the first scheduled run

Check the actual settings and first run history of the scheduled task you just made. Tell me whether the name, frequency, time zone, run environment, and input are as intended. If it hasn't run yet, mark it as not run. If it failed, explain the error and what to check next. Don't call it a successful run just because the schedule was saved.

Where people get stuck

Lots of people get stuck here. Find the one that matches your situation!

What to review when it fails

After saving a schedule, check the real run history — Click the picture to see it larger.

Schedules that use a local folder need your computer on and the app running. A web schedule won’t read that folder for you. Scheduled tasks also count toward your plan’s usage and permission limits.

Quick check: Does a desktop schedule that uses a local folder always run, even when my computer is off?

Answer: “No, check that the computer and app conditions are met”
Local tasks need that computer, the app, and file access. Keep them separate from web tasks.

Official sources

Official docs on scheduled tasks

Next tip

Add Context7 as a Codex plugin →

I'm stuck here

Stuck while following along? Tell me where. Only the site owner sees this. Leave your email only if you'd like a reply.