After spending 2 hours in chat with a lovely Hubspot support person, it has come to my attention that there is an issue with cloning event based delays and the subsequent event met/not met branching.
Where you clone an event based delay in a workflow, it will hardcode the event based delay criteria into the new branch, thereby checking the criteria from the initial point that you cloned the delay event at - that is, whether or not the criteria was met at the initial delay point NOT where the cloned step and branch has been placed.
It wont update and it cant be modified by the user to update and instead will branch people in the workflow down an incorrect branch, event if the event has ocurred.
This issue only ocurs with cloning event based delays, all other delay cloning is fine and can be modified.
The event based delay should be updated to either Not allow event based delay cloning in workflows OR to be able to modify the criteria it is using in the subsequent branch.
This information should also be shared in a knowledge article and to staff to support them in assisting HubSpot users.
Example shown below.
The original #9 and 11 was cloned to make #20 and #23. But point #23 is still reading whether the criteria was met at delay #9 and cant be udpated to instead be #20. Therefore if the event hadn’t been met at #9, the instead continue down the event not met branch at #23.
Hubspot please resolve. This will cost you time, money and a not so healthy amount of frustration until you identify it.
