Scheduled Tasks
Scheduled tasks run with a fixed profile tuned for short, practical, repeatable results.
| Property | Value |
|---|---|
| Model | Fast |
| Reasoning | Medium |
| Where it runs | On the server; it also runs while the app or your computer is off |
| Time limit | Up to 5 minutes per run |
| Context | The task's previous runs |
| Credits | Actual input and output token usage |
| On failure | The task is paused after 3 failed runs in a row |
Previous runs are used as context
Each run sees the task's earlier results and produces a short, practical result. That way a daily bulletin can avoid repeating yesterday's news, and a weekly follow-up can highlight what changed since last week.
Credit usage
- Each run deducts credits for its actual input and output token usage (see How are credits deducted?).
- Tasks that use web search or connected apps read more context, so they can use more credits.
- Keeping the instructions short and focused makes the result clearer and lowers credit usage.
Failed runs
- A run that doesn't finish within 5 minutes or stops because of an error counts as failed.
- After 3 failed runs in a row, the task is paused automatically. Once you've fixed the problem, start it again with Resume.
- Common causes: a disconnected app (see Disconnecting), instructions that are too broad, or not enough credits.