I build a workflow that is triggered, when column changes to any status. My status are company teams, so the workflow checks for said team and sets people column to teamlead. My reasoning is:
When people coloumn change, check if teamlead is A and set team A, if not - check if teamlead is B and set team B, if not - check if teamlead is C and set team C and so on. We’re up to 12 iterations of these kind.
My issue is: If teamlead is A and the workflow sets team A, it still checks all other options and resulting in unnecessary usage of automation runs. Why isn’t the worklow stopping if it meets one true condition?
And / or do you have any other ideas how to automatically set a status column based on a people column? I am using the status (team) column to display projects per team and accounting for changing teamleads.
Instead of a branch workflow, I’d recommend setting up a board that has your ‘data’. For this example, I have all states listed and then the appropriate sales person in the people column. Then when we get new leads, the workflow uses ‘Find Matching Item’ on the states board, gets item data and then updates column.
Monday automations don’t stop after a true condition—they check all if/then branches. Using a formula column to map teamlead → team or splitting automations per team usually works best.
Thanks Agatha! But logic would dictate a stop after one true condition. At least for me it would. Is there a database on how the triggers and actions work or is it learning on the raod?
@dmccarthy22710 I just duble checked. It did fetched my data, but the output is a numercial ID of them item and not the label-name itself. Could you work me through your worklfow?
For me it is as follows:
Entry of a new project and setting people column to my name.
“get data” → my need is: when people column is me (in this example) set department label Cockpit. But the worklow is translating the ID 12345678925 as a new label.
Hey! With Monday workflows, the if/then sets your condition, and stop trying else prevents unwanted actions when the condition isn’t met. It’s great for keeping automations clean. Testing on a small board first usually helps.
