Scheduled workflows’ overlapping execution

Avatar

Avatar
Give Back 50
Employee
Sukrity_Wadhwa
Employee

Likes

171 likes

Total Posts

931 posts

Correct reply

35 solutions
Top badges earned
Give Back 50
Validate 1000
Validate 500
Validate 250
Validate 100
View profile

Avatar
Give Back 50
Employee
Sukrity_Wadhwa
Employee

Likes

171 likes

Total Posts

931 posts

Correct reply

35 solutions
Top badges earned
Give Back 50
Validate 1000
Validate 500
Validate 250
Validate 100
View profile
Sukrity_Wadhwa
Employee

28-02-2021

In Campaign Standard, the workflow engine guarantees that a workflow instance is executed by only one process. Blocking activities such as imports, long running queries or writes into the database prevent the execution of any other task when running.

On the other hand, non-blocking activities do not block the execution of other tasks (usually activities waiting for an event such as the Scheduler activity).

This can lead to a scenario where a schedule-based workflow can start executing even when the previous run of that same workflow has not yet finished, potentially leading to unexpected data issues.

Therefore, when designing a scheduled workflow which includes multiple activities, you need to make sure that the workflow is not rescheduled until it is finished. To know how to make sure that a scheduled workflow is not rescheduled until one or more tasks from a previous execution is still pending, check this documentation: Scheduled workflows’ overlapping execution

 

In case you have any questions, please feel free to post them below or reach out through the community Q and A section. 
In case you have any ideas and/or suggestions regarding the Campaign Standard product, then kindly submit them here