Good to know, it's not just me. I may look into adding an action that fires off another workflow, so we can break a large workflow down into smaller ones. Do you think anyone else would be interested in that?

I've considered using multiple workflows, but we often need to reference data from the original.

We only need an entity (usually a person) passed to the next workflow. That should be straight forward. But perhaps if we also figured out how to pass the original workflow guid, then the new workflow could get whatever it needs from run sql. Would that cover your scenarios too?

Depending on the situation, that might work. Many of our existing workflows use a lot of attributes though. In those instances, it wouldn't be as useful.

I think we will have for solution on this in the next couple days. It will pass a person as the entity to the second workflow. It will also cycle through the attributes in workflow 1 and workflow 2, if any of the keys match, it will pre-populate them in workflow 2. I think that would cover your scenario, correct? We have the baseline working, already. We will be working on adding the attribute key matching, next.

Something else to consider is that we can/will be working on performance. You might consider crafting the workflows in a way that optimizes clarity vs performance. You may have to live with some slow performance in the short-term. But it will only get faster as we optimize. Just a thought...

Good point. Since your post, we've streamlined it. We cut about a third off the workflow. It's in production now. There is a lot more we want to do to it but probably need to revisit what can be put in custom actions, instead of directly in the workflow.

That said, even today, we ran into a new situation where a custom action that calls a second workflow, solves the problem. We got distracted with our launch but we'll probably finish that custom action soon.

Feel free to push your action to core if you think it's reusable. Sounds like something that a lot of folks would need.