When building a workflow, some actions you put in turned out to be unnecessary. These actions you would want to delete to save time and updates. But right now it’s hard to see the uses of individual actions inside a workflow, especially when the workflow gets complex.
As of now you need to pay very close attention when deleting an action inside a workflow so that you don’t break any other functionality accidentally.
I think it would be very helpful to have a function to be able to find all uses of actions within workflows like for column in the data editor.
When an action is included in a workflow isn’t it by definition already “in use”? (unless it’s disabled)
Yes it’s in use then, but that doesn’t mean it’s necessary to complete the workflow, and by letting it exist it’s using time, energy and updates. Therefore I would want to delete every action not necessary. Let’s say I’m building a complex workflow with a query in the beginning that I build actions upon, then notice that there’s a better way to deal with the problem that I’m trying to automate, so I delete a bunch of the workflow, but there I might risk breaking other parts in my workflow because I delete a part of it. In simple workflows you can remember it/keep the overview, but in my experience when you’re building complex workflows remembering all the uses for different actions is harder. Maybe the solution is just creating better documentation with each action but find all uses for actions seemed a better option, what do you think?
You need to vote on your own post