Snooze a schedule
well_snooze_scheduleSnooze one workspace routine: skip its runs until a moment the person names, then let it carry on by itself with the same rhythm. Use it when the person asks to skip a few days, take a break from a routine, or snooze it: "snooze my morning brief until Monday", "skip my brief this week", "no brief before the 20th". The routine stays armed and the person does not have to resume it.
REQUIRED: schedule_id (from well_list_schedules) and snooze_until, an ISO 8601 date and time with an offset, in the person's time zone. A day with no time means the start of that day, so "until Monday" lets Monday's run happen. The routine runs again at its first scheduled time at or after snooze_until. When the person gives a span and no date, do not ask for one: "a few days" is 3 days, "a week" is 7 days. Pick the date, snooze, and say it so the person can correct it.
Works on an active routine that runs on a clock. A routine that starts on an event has no clock to delay: the call is refused, so tell the user and offer to cancel it instead.
Do NOT use this to stop a routine: "disable my morning brief", "stop my brief" and "turn it off" use well_cancel_schedule. Do NOT use it to change the rhythm, the time or the job (use well_update_schedule), or to pause a routine until the user resumes it (use well_update_schedule with status "paused").
Snoozing draws no confirmation card. Say the date of the next run the result returns, in plain words.
When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| schedule_id | Yes | The routine to snooze. | |
| snooze_until | Yes | When the routine may run again, ISO 8601 with an offset, in the person's time zone. | |
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| idempotency_key | No | Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| status | No | ||
| message | No | ||
| success | Yes | ||
| schedule | No | ||
| next_run_at | No | ||
| approved_tools | No | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| resolved_workspace | No | The workspace that answered, when the caller named none and the token authorizes several. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. |