> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://catena.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://catena.ferndocs.com/_mcp/server.

# Schedule deactivated

POST 

Emitted when a schedule is deactivated.

Reference: https://catena.ferndocs.com/api-reference/notifications/webhook-events/schedule-deactivated

## Request

### Payload

- `version` (string, required) — Version of the schema used for this event
- `data` (list of BaseScheduleEvent, required) — The event payload, with one or more records of the specified type
- `webhook_id` (string, required) — Unique identifier for the webhook subscription that triggered this delivery
- `event_name` (string, optional, default: schedule.deactivated)
- `timestamp` (datetime, optional, nullable) — ISO 8601 timestamp when the event occurred
- `id` (string, optional, nullable) — Unique identifier for this specific event instance (UUID v7 for time-ordered sorting)
- `delivery_attempt` (integer, optional, default: 0) — The number of times the event has been attempted to be delivered

## Types

### BaseScheduleEvent

Base schedule event.

- `id` (string, required) — The ID of the schedule
- `connection_id` (string, required) — The ID of the connection used for this schedule
- `resource` (enum, required) — The resource type being scheduled for processing
  - Allowed values: `asset`, `document`, `driver_association`, `driver_vehicle_association`, `driver_event_log`, `driver_safety_event`, `dvir_log`, `dvir_log_defect`, `engine_log`, `engine_status`, `fuel_transaction`, `fuel_card`, `fleet_info`, `hos_availability`, `hos_daily_log`, `hos_daily_snapshot`, `hos_event`, `hos_event_annotation`, `hos_event_attachment`, `hos_violation`, `ifta_summary`, `location_segment`, `message`, `group_message`, `user`, `vehicle`, `vehicle_location`, `vehicle_sensor`, `vehicle_region_segment`, `trailer`, `trailer_association`, `trailer_vehicle_association`, `trailer_location`, `trailer_status`, `workflow`
- `execution_interval_seconds` (integer, required) — The interval in seconds between executions
- `status` (enum, required) — The status of the schedule
  - Allowed values: `active`, `inactive`, `paused`, `expired`, `cancelled`, `pending`, `deleted`, `stale`, `success`, `failed`, `scheduled`, `accepted`, `declined`
- `consecutive_error_threshold` (integer, required) — The threshold for consecutive errors before marking as failed
- `max_concurrent_executions` (integer, required) — The maximum number of concurrent executions allowed