Scenario
Say Workflow 1 executes on a ticket T1 when ticket is raised or ticket has an updated event.
As part of this Workflow 1 execution, another ticket T2 is created via a web request node.
Currently, up to 20 workflows (which did not execute on ticket T1) should execute on ticket T2 provided there are required matching events and conditions.
Current behaviour
Workflows that did not actually execute are wrongly counted as executed.
Definition of actual execution:
At least one action from the workflow has been executed on the ticket.
Only the condition evaluations should not be counted.
As a result, the limit of 20 is reached sooner than expected, resulting in few matching workflows not executing on ticket T2.
New behaviour after the fix
Up to 20 workflows, which have valid matching events and conditions will execute on the ticket T2.
Note: These 20 workflows are those, which would not have executed on ticket T1.
What is expected from customers
Review workflow configurations where web request nodes are configured to create tickets.
Note that on the tickets created by workflow automation, other workflows which are matching (and have not executed on the original ticket) will start executing from now on.
Make the required configuration changes accordingly.
