MNI vs Looping for start process smart service

Yes, sub-processes run on the same engine as the parent process.

As someone else suggested, it would be helpful if you could elaborate a bit more on your use case. Given that Health Check is flagging this as a risk, it may be worthwhile to come at the problem from a different angle altogether. With more information about your use case, the community might be able to help you brainstorm other ways to meet your requirements, while still adhering to best practices.

Thanks eliot ,

scenario is we will be getting Requests via Database as new records.

We want all of these to be processed , So a scheduler picks up these request ona given time interval as a batch and tries to kick off Different Appian process instances for each of these requests.

So am trying to understand the pros and cons of using MNI or Looping to start the destination process models in a better way such that performance of the server doesnt gets degraded.

Regards,
Thoufiq.

Thanks eliot ,

scenario is we will be getting Requests via Database as new records.

We want all of these to be processed , So a scheduler picks up these request ona given time interval as a batch and tries to kick off Different Appian process instances for each of these requests.

So am trying to understand the pros and cons of using MNI or Looping to start the destination process models in a better way such that performance of the server doesnt gets degraded.

Regards,
Thoufiq.