A scheduled task is one concrete action at one future date and time. Ask the responsible agent to create it. Use a recurring schedule only when the work should repeat.
An objective with a due date is a tracking record, not a timer. A note saying “tomorrow” is not a scheduled execution. Look for a successful saved scheduled-task result.
State the action and the time
- Open the project conversation for the work, or Space assistant for a personal reminder.
- Give the exact action and the document, sheet, or source it should use.
- State a future calendar date, local clock time, and named time zone.
- Specify the result destination and any review or external-action boundary.
- Ask for confirmation of the saved task, assigned agent, execution time, and destination.
Example to adapt with a real future date:
On [date] at 14:00 Europe/Berlin, read the project launch checklist and summarize unfinished items in this chat. Do this once. Do not edit the checklist or send anything externally. Confirm the saved scheduled task and its time.
A real task is created by create_scheduled_task. Its source-backed time validation requires a future timestamp with an explicit UTC offset plus a valid named time zone. The agent can translate your ordinary-language request, but you should still check the saved date and time, especially around a daylight-saving change.
This creation flow was not executed in the documentation demo.
Choose the correct agent and scope
A project manager can manage one-off tasks for itself or current project team agents. A specialist can schedule and manage its own tasks. The Home assistant can schedule only itself in your Home conversation.
Personal Home reminders do not appear as project workflows. Project work should be scheduled in the appropriate project. Missing tools, connections, or permission still need to be resolved; future execution does not grant the agent access it lacks now.
For how chats and external reports are attached, read Recurring schedules. Persistent team uses the assigned agent's ongoing project conversation; Flexible chats can use a compatible connected chat or independent run history.
Find upcoming tasks and history
Ask the project manager for a project-wide list; a team agent can list only its own tasks. For the manager:
List this project's upcoming scheduled tasks with their assigned agents, times, and current states. Do not create another task.
The source-backed project route is Workflows → Scheduled tasks, with Upcoming and History. Successful, failed, and cancelled items appear in history. You can also ask the agent to list pending, running, succeeded, failed, or cancelled tasks.
A task being queued is not proof it completed. Check the actual result and any external destination separately.
Reschedule an existing task
Move the pending Launch checklist review to [new date] at 10:00 Europe/Berlin. Keep the action and destination. Confirm the replacement task and that the old time is cancelled.
Rescheduling applies to pending tasks. Current source cancels the old record and creates a replacement with a new task ID. If a sheet or Mini App stored the previous ID, update that reference rather than treating the replacement as an unexplained duplicate.
The agent reschedule tool changes timing and destinations. It does not directly rewrite the task title or instructions. For an instruction change, the agent may need to cancel and recreate the pending task; ask it to confirm that only the intended future action remains.
Cancel a pending action
Cancel the pending Launch checklist review. Confirm its cancellation and tell me if it has already started.
cancel_scheduled_task cancels pending work. It does not stop a running task. If execution has started, use its active-run Stop control where available and inspect what already happened. Cancellation is not a rollback of completed external effects.
Source-backed interface controls
Expanding a pending task in the project list exposes Reschedule, Run now, and Cancel task. Reschedule offers New date and time → Save new time; cancellation has a confirmation.
Run now queues an execution. A queued confirmation is not a completion result. Do not use it to test a task that would send, publish, buy, or modify something unless that immediate action is intended.
The general project reschedule interface uses the browser's time zone when submitting. The Home editor has an explicit time-zone control. Review the displayed time instead of assuming the two screens behave identically.
These controls are source-backed, not live-tested in this preview. The chat-first route is usually easier when the action, time zone, and scope need to be stated together.
Avoid duplicate actions
Before retrying an uncertain creation or reschedule, ask the agent to list matching tasks and inspect their states. Keep a source-item reference for actions tied to a specific record. The creation tool supports an idempotency key for deliberate retry protection; do not assume every natural-language request automatically deduplicates an earlier request.
For repeated work, use Recurring schedules. For incoming-event work, use Channels and triggers.