Are unattended nodes included in the limit of consecutive chained nodes?

I had a similar issue not long ago. Here's the link to the conversation forum.appian.com/.../e-67771

The short answer is yes, unattended nodes are included in the count. Because my case varied widely in how many instances some nodes are running I built a waiting screen that checks a status variable to clear before moving forward. When I get the time, I plan on reevaluating my process to avoid running multiple instances all together. Another option is to increase the chained node limit. That info is here. forum.appian.com/.../Configuring_the_Process_Engine_Servers

Thanks James. We've already increased the limit and removed any loops or MNI.

@alastairw Can you share what you did? I also need to do workaround on the subprocess limit and MNI, try using multiple instances on the subprocess,but the problem is I can't get the index of the data per row (ex. index(pv!col3,pv!count), since i remove the MNI and no tp!instanceindex in subprocess, i'm having hard time what to put on the indexNo parameter). My scenario here is uploading CSV files and processing each row using a subprocess. WOuld appreciate your help. TIA

You'll want the fv!index property of the a!forEach function for that. Your workaround is to use the forEach function in a script task you call once for all your data, and handle indexing using that. If you don't have 16.3 or higher, that would be a huge incentive I think to get approval for upgrading.