docs: clarify schedule administration names

This commit is contained in:
lda
2026-09-10 05:36:58 +07:00 Verified
parent a11a7745c9
commit cced1b4c2d
@@ -351,10 +351,13 @@ its executing mark and ACTIVE attempt for startup recovery to abandon
truthfully), and releases ownership last. truthfully), and releases ownership last.
A failed startup releases the lock and raises. A failed startup releases the lock and raises.
Administration (`WorkflowApi` schedules methods, `workflow.schedules.*` Administration is available through the `WorkflowApi` schedule methods,
RPC, Python client): `create/get/list/update/pause/resume/delete_schedule` `workflow.schedules.*` RPC, and Python client. The API/transport operations
plus paginated `list_schedule_occurrences`. Creation validates the are `create_schedule`, `get_schedule`, `list_schedules`, `update_schedule`,
trigger, the deployment, the binding shapes, and a sample-occurrence `pause_schedule`, `resume_schedule`, `delete_schedule`, and paginated
`list_schedule_occurrences`; the Python facade maps them to the names listed
above. Creation validates the trigger, the deployment, the binding shapes, and
a sample-occurrence
resolution against the pinned root schema, and starts the consumed resolution against the pinned root schema, and starts the consumed
watermark at creation (no pre-creation backfill). Updates are watermark at creation (no pre-creation backfill). Updates are
revision-checked; pause/resume/delete mirror the poll-loop transitions; revision-checked; pause/resume/delete mirror the poll-loop transitions;