I wonder if those ‘make changes total’ could be one step instead of running them after each ‘thing’ update.
I would like to test this because I’m not sure, but maybe DB Triggers would be an option for something that complex? Example: update other/blank only when “other/blank SKU.name-before change IS NOT other/blankSKU.name” or something.
Basically it’s checking to see if the value was actually changed before doing that workflow. If there are a bunch of ‘do searches’ in those ‘make change’ steps, that’s probably the reason.
Although, to spike to almost 800K runs, something seems off.