Skip to main content

Named schedules

Deterministic named-schedule CRUD, revision conditions and retained retry outcomes.

📄️listNamedSchedules

Requires `agents:read`. Deterministic stored configuration only; no worker/network/provider reachability evidence. New mutations require API_CONFIGURATION_ENABLED, Idempotency-Key and (except schedule creation) an exact If-Match ETag. Current authority precedes retained replay; matching replay returns the original outcome before testing its historical conditional revision. Disable/delete do not cancel an admitted occurrence. Setup controls require a member-issued key; service credentials may only use explicitly granted named schedules.

📄️createNamedSchedule

Requires `agents:manage`. Deterministic stored configuration only; no worker/network/provider reachability evidence. New mutations require API_CONFIGURATION_ENABLED, Idempotency-Key and (except schedule creation) an exact If-Match ETag. Current authority precedes retained replay; matching replay returns the original outcome before testing its historical conditional revision. Disable/delete do not cancel an admitted occurrence. Setup controls require a member-issued key; service credentials may only use explicitly granted named schedules.

📄️getNamedSchedule

Requires `agents:read`. Deterministic stored configuration only; no worker/network/provider reachability evidence. New mutations require API_CONFIGURATION_ENABLED, Idempotency-Key and (except schedule creation) an exact If-Match ETag. Current authority precedes retained replay; matching replay returns the original outcome before testing its historical conditional revision. Disable/delete do not cancel an admitted occurrence. Setup controls require a member-issued key; service credentials may only use explicitly granted named schedules.

📄️updateNamedSchedule

Requires `agents:manage`. Deterministic stored configuration only; no worker/network/provider reachability evidence. New mutations require API_CONFIGURATION_ENABLED, Idempotency-Key and (except schedule creation) an exact If-Match ETag. Current authority precedes retained replay; matching replay returns the original outcome before testing its historical conditional revision. Disable/delete do not cancel an admitted occurrence. Setup controls require a member-issued key; service credentials may only use explicitly granted named schedules.

📄️deleteNamedSchedule

Requires `agents:manage`. Deterministic stored configuration only; no worker/network/provider reachability evidence. New mutations require API_CONFIGURATION_ENABLED, Idempotency-Key and (except schedule creation) an exact If-Match ETag. Current authority precedes retained replay; matching replay returns the original outcome before testing its historical conditional revision. Disable/delete do not cancel an admitted occurrence. Setup controls require a member-issued key; service credentials may only use explicitly granted named schedules.

📄️disableNamedSchedule

Requires `agents:manage`. Deterministic stored configuration only; no worker/network/provider reachability evidence. New mutations require API_CONFIGURATION_ENABLED, Idempotency-Key and (except schedule creation) an exact If-Match ETag. Current authority precedes retained replay; matching replay returns the original outcome before testing its historical conditional revision. Disable/delete do not cancel an admitted occurrence. Setup controls require a member-issued key; service credentials may only use explicitly granted named schedules.

📄️enableNamedSchedule

Requires `agents:manage`. Deterministic stored configuration only; no worker/network/provider reachability evidence. New mutations require API_CONFIGURATION_ENABLED, Idempotency-Key and (except schedule creation) an exact If-Match ETag. Current authority precedes retained replay; matching replay returns the original outcome before testing its historical conditional revision. Disable/delete do not cancel an admitted occurrence. Setup controls require a member-issued key; service credentials may only use explicitly granted named schedules.