Actions76
- Incident Actions
- Severity Actions
- Status Actions
- Type Actions
- Custom Field Actions
- Custom Field Option Actions
- Schedule Actions
- Schedule Entry Actions
- Escalation Actions
- Catalog Type Actions
- Catalog Entry Actions
- Action Actions
- Follow-Up Actions
- Alert Actions
- Alert Attribute Actions
- Alert Route Actions
- Alert Source Actions
- Alert Event Actions
- User Actions
- Workflow Actions
- Incident Attachment Actions
- Incident Membership Actions
- Incident Update Actions
- Incident Timestamp Actions
- Incident Relationship Actions
Schedule → Update
AI-generatedSummary
Update an existing schedule using its ID, modifying its name, timezone, and configuration.
Inputs
- scheduleId (required) — The ID of the schedule to be updated.
- name (required) — New name of the schedule.
- timezone (required) — Timezone for the schedule (e.g., Europe/London, America/New_York).
- config (required) — Schedule configuration (JSON format with layers).
- requestOptions — Optional settings for the request, including batching options and timeout.
Output shape
no body — success/failure only
Returns success or failure status; does not return updated schedule details.
Examples
Example 1: A user wants to update the schedule named 'Night Shift' to 'Night Shift Updated', changing its timezone to 'America/New_York' and providing a new configuration.
Parameters: scheduleId as '1234', name as 'Night Shift Updated', timezone as 'America/New_York', config as '{"layers": [{"name": "Layer 1"}]}'.