Multiple short workflows vs a few more complex ones

[Edyta7510]

Hi All, 

I've realized I've got the tendency to create multiple short workflows on my account (vs. more complex ones based on if/then branch). At this point, organizing them in folders still does the job. 

I was wondering though what is the impact of multiple workflows on account performance? Are they slowing it down? What is the best practice: create less but more complex workflows? or the other way round? Both do the job "functionally" of course. 

Thanks!

Edyta

[karstenkoehler · Accepted solution]

Hi @Edyta7510,

I don't have information on the backend performance but would expect large number of simple workflows to consume more processing power than fewer more complex ones – mostly because (like active lists) each workflow has to constantly check all records and whether they match the enrollment triggers.

That being said, in many years working with workflows, I haven't noticed a considerable difference in portals who mostly pursue one or the other "style" of creating workflows.

Personally, I'm also a fan of a modular approach that leans towards simpler workflows (and hence more of them), since they're easier to maintain, troubleshoot and less prone to error. I will not go out of my way to break workflows into smaller bits however, for example if it could be done with straight-forward branching logic. If you have specific examples, we can happily discuss them.

With a solid naming convention, having a lot of assets should not be a problem. Workflows will start to pile up either way at some point.

Hope this helps!

[Edyta7510]

Thanks @karstenkoehler This is a very helpful answer, I'll continue applying common sense to my workflows then 🙂 

[karstenkoehler · Accepted solution]

Hi @Edyta7510,

I don't have information on the backend performance but would expect large number of simple workflows to consume more processing power than fewer more complex ones – mostly because (like active lists) each workflow has to constantly check all records and whether they match the enrollment triggers.

That being said, in many years working with workflows, I haven't noticed a considerable difference in portals who mostly pursue one or the other "style" of creating workflows.

Personally, I'm also a fan of a modular approach that leans towards simpler workflows (and hence more of them), since they're easier to maintain, troubleshoot and less prone to error. I will not go out of my way to break workflows into smaller bits however, for example if it could be done with straight-forward branching logic. If you have specific examples, we can happily discuss them.

With a solid naming convention, having a lot of assets should not be a problem. Workflows will start to pile up either way at some point.

Hope this helps!

[BBaumgardner]

Hi @karstenkoehler !

I know this is an old comment, but I'd be curious if you have any speciifc recommendations for Workflow naming conventions. We're getting to the point that these are starting to get pretty complicated and I'd like to go back and clean them up before it gets out of hand.

Thanks!

[karstenkoehler · Accepted solution]

Hi @BBaumgardner, I answered a similar question two days ago here 🙂