Strange Behavior in big Workflow - Large Memory use and "TimeOut" on FlowDecision

Description

I have created a big workflow working on eInvoices. A parent Workflow dispatches child Workflows and in certain situations the RAM and CPU usage goes rampant making the system and server unresponsive.

Steps to Reproduce

Am not sure how easy it is to reproduce my setup, at there is a lot of databases, files etc. There is a certain FlowDecision Node evaluating a workflow variable “IsValid”, if it is “False” it saves some data and creates a bookmark, this works perfectly. If the variable is “True” the workflow goes a different route, but the RAM/CPU goes rampant using 10+gb ram and it is stuck in the FlowDecision for 8 minuttes, if I can believe the execution log

Reproduction Rate: Always

Video/Screenshots:

1st screenshot shows the instance execution of 3 flows, two performing by entering a suspend state correctly, when the variable IsValid = false. Is the workflow named “4-xxx” that has problem and its called from the “3-xxx”

And the latest one finishing after 8 minuttes, because it is true and using 10gb ram

2nd screenshots shows the “false” route and 3rd screenshot the execution details on the FlowDecision Activity

4th screenshot show the instance execution where the variable is true and the 5th screenshot the execution time etc.

Is this execution start and stop time valid ?, because then it is stuck in a 8 minute FlowDecision or can it be somewhere else but reporting this ? Is there something am overlooking here ? Maximum of nodes/activities ?

Environment

• Elsa Package Version: 3.8.1
• Operating System: Windows Server 2019, also on Windows 10 and Windows 11.
• Browser and Version: Studio 3.8.1 Firefox starts the workflows.

Troubleshooting Attempts

I have tried to make the FlowDecision always “True”, to examine variable issues, but the problem remains the same. I have deleted the original FlowDecision and made a new one, same result. If I remove the FlowDecision completely and send all workflows in the “true” route, they all process correct and fast. No RAM or CPU spikes

Additional Context

Is there anyway for me to share more information or any pointers anyone can share on an issue on a similar problem