Update an existing schedule.
ManageOrgSchedules permission at the organization level.
enabled to false.
Setting playbook_id to null will clear the associated playbook.
You can change the schedule_type between recurring and one_time. When changing to one_time, provide scheduled_at with a future ISO 8601 datetime. When changing to recurring, provide frequency with a valid cron expression.
run_as_user_id parameter controls which user identity the schedule runs as. When a schedule fires, sessions are created under this user — they receive notifications and the session appears in their history.
ImpersonateOrgSessions permissionUseDevinSessions permissionnull): Reverts the schedule to run as the default bot userService User credential (prefix: cog_)
devin, data_analyst, advanced always, failure, never recurring, one_time Set the user ID that this schedule will run as. Requires ImpersonateOrgSessions permission. The target user must be a member of the organization. Setting to null reverts to the default bot user. Omitting the field leaves the current identity unchanged.
Successful Response
devin, data_analyst, advanced always, failure, never recurring, one_time