Documentation

ScheduleOverlapPolicy : int
in package

Controls what happens when a workflow would be started by a schedule, and is already running.

Tags
see
ScheduleOverlapPolicy

Table of Contents

Cases

AllowAll  = 6
Start any number of concurrent workflows. Note that with this policy, last completion result and last failure will not be available since workflows are not sequential.
BufferAll  = 3
Buffer up any number of starts to all happen sequentially, immediately after the running workflow completes.
BufferOne  = 2
Means start the workflow again soon as the current one completes, but only buffer one start in this way.
CancelOther  = 4
If there is another workflow running, cancel it, and start the new one after the old one completes cancellation.
Skip  = 1
Default.
TerminateOther  = 5
If there is another workflow running, terminate it and start the new one immediately.
Unspecified

Cases

Skip

Default.

Don't start anything. When the workflow completes, the next scheduled event after that time will be considered.

BufferOne

Means start the workflow again soon as the current one completes, but only buffer one start in this way.

If another start is supposed to happen when the workflow is running, and one is already buffered, then only the first one will be started after the running workflow finishes.

BufferAll

Buffer up any number of starts to all happen sequentially, immediately after the running workflow completes.

CancelOther

If there is another workflow running, cancel it, and start the new one after the old one completes cancellation.

TerminateOther

If there is another workflow running, terminate it and start the new one immediately.

AllowAll

Start any number of concurrent workflows. Note that with this policy, last completion result and last failure will not be available since workflows are not sequential.


        
On this page

Search results