For the recent days I have been fighting with the 5.1 release for a solution of backend batch processes.

For multi-threading, I take an alternative that put the logic in a Thread instance, and start it in the work item handler. Further more, for time consuming tasks, even it's in main signle process, since I found the console was actually running all processes in one main thread, I put the logic in a Thread instance too, and put a signal event after the task. When the thread finishes, it sends back a signal to the process instance and the process will continue. This can make the main thread less occupied, so that other processes can have time to run. These are all alternatives since the framework itself cannot satisfy my expectation by default.

Now I'm thinking how to start one process by another in a fire-and-forget manner. I did some test. By default, even I set the sub-process's "wait for completion" to "false", the parent process would still wait for sub's completion. The exception seems to be that when the sub met some event node, say a timer, even with "delay" set to 0ms, the parent could take the running back.

So I'm thinking to put a timer at the beginning of the sub, right after the start node, which would be another alternative.

Could you kindly advise, whether there are any more appropriate means to fulfill the expected functionalities?

BTW, I see there is a "Timers" property in some task nodes. But there seems no corresponding content in the user guide. Could you advise on it's function as well?

Thanks,

Bruce