Hi!
I have a playbook that gets stuck in a very weird way. I seek for community help as after my last session with product support, i do not seem to go anywhere as there were no obvious platform errors, they blame the playbook. 😞
Since the upgrade to the latest 6.14 build, one popular custom playbook is stuck on specific conditional task. It clearly shows that the condition matches, however the further tasks are not started. Even more, after that i cannot reopen any other incident task, cannot rerun playbook, cannot close the incident. No errors observed, platform just ignores my commands. Notable, that incident only gets stuck if there is a match, if the condition "else" is matched, it goes through with no issues. The only way to unstuck i found, is to restart demisto service on backend.
I tried many other things with modifying the task and the playbook in general, gradually removing other tasks, however i can't locate any broken task, link or anything obvious not working. I fully rebuilt the conditional task in question to have a very generic match, same result.
So the issue in it's core is that playbook execution halts just after the conditional task match, apparently on some content that is is behind an inactive branch, rather than on active.
Since the playbook is quite big, i thought i could delete some tasks in groups to find if there's something causing an issue. I stumbled upon another behavior - when removed certain parts of (inactive) branch tasks, the playbook would get stuck at the same conditional task for ~3min, and then it would be "released" and continue normally. So definitely the further content of the playbook does impact the execution flow, even it is not yet executed. Eventually, after removing some tasks, the playbook is being executed fine. However i can't locate a single task that causes this.
In the picture - simple test condition is matched, however no execution on next task. Note, the inactive branch contains quite a big collection of other tasks. To my eyes, inactive branch should be ignored by the runtime, but apparently it is not.
I would appreciate any ideas of how to troubleshoot, thank you!
Antanas
