Disable Schedule

Scheduler prerequisites

Configure an AgentOS-level database with schedule methods. The example scheduler server uses SQLite. Database-backed schedule CRUD is available without starting the scheduler; execution requires scheduler=True, a running application lifespan and a scheduler_base_url matching the server's address.

Owners come from authenticated identity. Configured authorization uses schedules:read, schedules:write and schedules:delete. Creating, repointing, enabling or triggering a run schedule also requires permission to run its target. Non-run targets require admin permission when that authorization is enforced. An inaccessible record can return 404; insufficient permission returns 403.

Disabling prevents future scheduled triggers. It does not cancel an already executing component run. The response contains the schedule's updated enabled state.

curl --request POST 'https://example.com/schedules/string/disable'

{  "id": "string",  "name": "string",  "enabled": true,  "next_run_at": 0,  "updated_at": 0}

{  "detail": [    {      "loc": [        "string"      ],      "msg": "string",      "type": "string",      "input": null,      "ctx": {}    }  ]}