Academy
5. Schedules: Recurring Tasks on Autopilot
Forge a recurring task from a plain-language description, attach it to a durable task, and use pause, resume, fire-now and history to manage it.
A schedule is a recurring task that runs on autopilot. Instead of manually launching the same mission every day or every week, you describe what to produce and when — in plain language — and OUPI forges a schedule for you. Each scheduled run delivers into a durable task: a persistent folder that keeps its context, files, and the full history of every run. This means each execution builds on the previous ones rather than starting from scratch, making it ideal for weekly reports, monthly articles, or any repeating deliverable. You can also opt to receive the output files by email after each run.
To create a schedule, use the "Forge a recurring task" option in Studio. Write a plain-language description that includes two things: (1) what to produce — the outcome, audience, and format — and (2) when to run — e.g., "every morning at 8" or "every Monday at 9 AM." OUPI interprets your description, creates the schedule, and automatically attaches it to a durable task folder. There is no cron syntax to learn; the agent parses your intent from natural language. The cost of each run is proportional to the work done and is shown per run, so you stay in control of credit usage.
Once a schedule exists, you manage it from the same place in Studio (Durable tasks). Four controls matter:
• Pause — Temporarily stops the schedule. No runs fire until you resume. • Resume (Arm) — Reactivates a paused schedule so the next occurrence fires on time. • Fire now — Triggers an immediate run outside the normal cadence, perfect for a live test before relying on the schedule. • History — Lists every past run with its result and verification verdict (verified, failed, or could not be verified), so you can audit what happened and when.
These controls also appear in the Assistant under Wake-ups, giving you a second access point.
Before trusting a schedule in production, always use "Fire now" to run it once and inspect the deliverable and its verification verdict. This catches brief-writing issues early — before the schedule runs unattended at 6 AM on Monday.
Write your schedule description the same way you'd write a good mission brief: state the outcome, the audience, and the format. For example: "Every Friday at 5 PM, compile a one-page summary of this week's support tickets for the ops team, as a PDF." Clear goals keep each run fast and cost-effective.
Go to Studio → Durable tasks. Click "Forge a recurring task" and type a description like: "Every weekday at 9 AM, draft a short market-news digest for my team as a document." Let OUPI create the schedule, then hit "Fire now" to test it. Check the deliverable in the durable task folder and read the verification verdict. Finally, pause the schedule.
Schedules let you automate recurring work with a plain-language description — no technical syntax needed. Every schedule is anchored to a durable task that preserves context and files across runs. Use Pause and Resume to control when it fires, Fire now to test instantly, and History to audit past runs and their verification verdicts. Pair a clear brief (outcome + audience + format + cadence) with a test run, and your recurring tasks will deliver reliably on autopilot.