I have the interface with nearly 40+ different fields which we collect and update the DB. In general everything is going good. After we got new requirement and because of new requirement we have add new subprocess model which will update the DB using Odata. So above process model has two subprocesses which will update data using Odata. If we have less number of data two subprocess models are getting completed and showing the page at end without any issues. If data is more(around 40 changes) then process model is breaking in middle and going to previous page(I mean from which page we have started it). But data is getting updated and if I see the monitoring page, then it is showing as everything completed successfully. But chain is breaking in middle and we are able to see Action Completed popup and redirecting to previous page. If we don't see Action Completed then I am not able to see previous page
The chaining can get broken for two reasons:
Do we need to consider nodes created during runtime based on data or while designing process mode itself. Because we don't have 50 nodes in chain, but still we are seeing issue
It's the total number executed at run-time. As I said, this is one of the reasons why you may be getting a break in the chain. Another is that you actually have a missing chain in one of your transitions (it's very easy to overlook one, especially if you have your thread spread over several different process models)
Do your subprocesses have loops? Unattended loops?
Because if you loop through more than 50 nodes it will break.
That means, if you have 11 nodes in one of the subprocesses, it will surely break trying to process 5 records, if you do one loop per record.
I think the key to really being able to help is understanding of what's in those subprocesses, unless what Stewart and I have explained is enough.
Discussion posts and replies are publicly visible
© 2020 Appian. All rights reserved.