List schedule runs
well_list_schedule_runsList the runs of one routine of this workspace, newest first: each run's status, when it was planned (scheduled_for), when it started and finished, its summary, warning_message and skip_reason, and the thread it ran in.
Use it to answer "did my Monday reminder run?", "why did the routine fail last week?" or "show me all the runs of this routine", past the last runs that well_list_schedules carries. Pass the schedule_id from well_list_schedules. Page to older runs with cursor from the previous result's next_cursor. A skipped run with skip_reason "sunday" was held back on a Sunday in the user's time zone: say it was skipped for Sunday, not that it failed. Quote what it returns; never state a status it did not report.
Do NOT use this to change, pause or cancel a routine (use well_update_schedule, well_snooze_schedule or well_cancel_schedule).
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 |
|---|---|---|---|
| limit | No | Runs to return, at most 50. Default 20. | |
| cursor | No | The next_cursor of the previous page, to read older runs. | |
| schedule_id | Yes | The schedule_id of the routine whose runs to list, from well_list_schedules. | |
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose 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. | |
| 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 |
|---|---|---|---|
| runs | No | ||
| error | No | ||
| status | No | ||
| message | No | ||
| success | Yes | ||
| schedule | No | ||
| next_cursor | 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. |