Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Best practice to handle hundreds of workflows

Avatar

Avatar
Validate 1
Level 2
johanna_m
Level 2

Likes

13 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
johanna_m
Level 2

Likes

13 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
johanna_m
Level 2

21-06-2019

What would be the best approach to recommend if a client has 300+ workflows running? in terms of performance

  1. What could indicate if a client is running 300+ workflows on their marketing instance? poor implementation? lack of product knowledge?
  2. In terms of performance issues? whats the best approach to handle such load?

At most, the max number of automated scheduled workflows I've seen running on a client is less than 100.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 10
Employee
craigthonis
Employee

Likes

167 likes

Total Posts

256 posts

Correct Reply

152 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 50
View profile

Avatar
Give Back 10
Employee
craigthonis
Employee

Likes

167 likes

Total Posts

256 posts

Correct Reply

152 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 50
View profile
craigthonis
Employee

21-06-2019

Hi Johanna,

So the number of scheduled workflows doesn't matter so much as to how many are executing at the same time.  So as long as these scheduled workflows are staggered to execute at different times then they should be fine performance wise.  The one exception to this is workflows in a paused status or using keep interim results as the build up in temp table data can cause significant performance issues even when not actively executing.

Now if the workflow executions are overlapping then we could potentially run into performance issues depending on the types of queries being run or the number of executions occurring at once.

If workflows are making inserts/updates to tables for example, then those tables get locked during that process, so if you have multiple workflows attempting to access a locked table then those workflows will need to wait for the inserts/updates to complete.

Whether or not there is poor implementation or lack of product knowledge would really require a discussion with the client to understand what the workflows are for and to see if there is a way to consolidate existing workflows.

If they have numerous data import/export workflows for example, it may make more sense to use external signals or jump points instead of schedulers to trigger off the next workflow versus having them on schedulers, that way you won't have any overlap in execution.

Unfortunately to recommend more would really require further review of the client's environment and a good understanding of what these workflows are trying to achieve.

Regards,

Craig

Answers (0)