You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since schedules are picked up based on nextRunningTime, a schedule can be considered paused for a cycle by simply updating their nextRunningTime to their next cycle's time.
For example, if a schedule was supposed to run every hour and the next invocation time is 1PM, if we update it to 2PM, it will not be picked up in the 1PM cycle and can be considered pasued for that duration.
Expose an endpoint that pauses the schedule based on this method for a given number of cycles.
Structure
POST /v1/schedules/{{identifier}}/pause
{"cycles": <int>}
Similarly, expose an endpoint to resume a paused schedule. Resuming in this context would mean, simply calculating the nextRunningTime based on their original period and setting that as the new nextRunningTime for the schedule.
Structure
POST /v1/schedules/{{identifier}}/resume
The text was updated successfully, but these errors were encountered:
Since schedules are picked up based on
nextRunningTime
, a schedule can be considered paused for a cycle by simply updating theirnextRunningTime
to their next cycle's time.For example, if a schedule was supposed to run every hour and the next invocation time is 1PM, if we update it to 2PM, it will not be picked up in the 1PM cycle and can be considered pasued for that duration.
Expose an endpoint that pauses the schedule based on this method for a given number of cycles.
Structure
/v1/schedules/{{identifier}}/pause
Similarly, expose an endpoint to resume a paused schedule. Resuming in this context would mean, simply calculating the
nextRunningTime
based on their originalperiod
and setting that as the newnextRunningTime
for the schedule.Structure
/v1/schedules/{{identifier}}/resume
The text was updated successfully, but these errors were encountered: