Discussion posts and replies are publicly visible
We have designed the web api like this , and we realized recently, the web api returns information without the process had finished when it has so much subprocesses, We have a problem.
So after some testing it looks like you can start a process within a WebAPI using a!startProcess and return the value of a process variable at the point that chaining is broken or the process end. Chaining could break due to an un-chained connection, a timer event, exceeding the maximum node limit, etc.