Scheduled tasks

Scheduled tasks let the agent or an app do things on a timetable: “brief me on my calendar and inbox at 8:00 every weekday”, “sync inventory every hour”, “remind me to send the weekly report next Friday at 3 pm”.

Creating one

1. Tell the agent in a workspace what you want to run on a schedule, or open Scheduled under Apps in the sidebar and start from an example.
2. The agent confirms with you:
   • what the task does;
   • which workspace and resources it uses;
   • how often it runs;
   • the timezone (tasks on local clock time need an explicit timezone; Gosper won’t guess).
3. The agent registers the task. A registered task starts disabled and doesn’t run yet.
4. Enable it in the workspace’s Connections panel to start the schedule.

Three kinds of timing

Kind	Good for	Notes
Fixed interval	Every 15 minutes, every 6 hours	Measures elapsed time, minimum 60 seconds; drifts against local clocks across daylight saving changes
Local clock time	Hourly, daily at 8:00, Mon/Wed/Fri	Runs on local wall-clock time and keeps it across daylight saving changes
Once	A specific moment	Runs once, then ends

Recurring tasks can be bounded: a number of runs (say, 10), or until a given time.

How runs behave

• Missed runs are skipped. Times missed while the service was unavailable aren’t replayed.
• Failures retry. A failed run retries up to 8 attempts, starting one minute apart and backing off to at most an hour. Retries don’t use up the run count.
• Exhausted retries stop the schedule. It shows Needs attention so you can check why.
• Access is checked before every run. If the workspace, connection or account is no longer allowed, that run is skipped.

Reviewing schedules

Scheduled under Apps lists the schedules across all your workspaces. Search, check status, and select a row to open its workspace. This page is for viewing; enable and disable in the workspace’s Connections panel.

Common states:

• Finished: a one-time task ran;
• completed: reached its run count or end time;
• expired: its end time had already passed when enabled, or a one-time moment passed;
• Needs attention: retries ran out and it stopped.

Note

Disabling and re-enabling starts a fresh count but keeps the original rhythm, and doesn’t replay missed runs. Workspaces created from a blueprint don’t copy schedules; register and enable them again.