Error while calling a subprocess

@chetany I remember I have seen this some months before, I might be wrong but I believe that the process will run properly if the node is restarted. Further I guess that this is raised because of the privilege issues, either in the process security or the actions that are carried out in it. In order to confirm this, configure the lane with 'Run as whoever designed this process model' option and run the process again.

I have faced this issue but no resolution. Just trying again same things works. I was facing such issue when kdb of environment got corrupted and they were renamed for restoration. Had your environment faced any such kind of issues? Was it corrupted in past?

Is it a new model to the environment? You could also try executing the process individually as this should force it to be loaded from design into all of your execution engines.

Hi Tim, Yes it is a new model. I will try executing it again. @umeshkumarn720, the environment was not corrupted. @sikhivahans, I have set the security and also configured the lane as "Run as whoever designed this process model."

@tim.clarke, I did not get that errror again. This time it ran fine. Does such issue happen occasionally?

Yes I have seen it before but rarely and that was the solution given by Appian. I've never understood the reasons why unfortunately.

Even we have experienced it for 2 to 3 times but there after it isn't ever seen. And restarting the node resolves the issue as well.

When a new model is imported into an environment it gets propagated from the Process Design Engine to the Execution Engines so that these last engines can instantiate it as a sub-process as part of a running instance.

Under some edge cases when an import is done during high load the model might not fully propagate to the EXEC engines. In that case you can still launch the process model as a standalone (since this happens in the Design engine) but not as a sub-process (which happens in the EXEC engines) generating this error:

"Process model not found on Execution server for sub process invocation. A Request to Design server has been made."

This error has nothing to do with security at all.

To address the issue we need to force the propagation of the model to the EXECs. The way you do it is you start a new instance of the model used in the sub-process activity throwing the error but you start it as a standalone process not as a sub-process.

Start several dummy instances like this until there's at least one instance on each EXEC engine. You can check this by using a report with a column defined as

=process_ee_id()

which shows on what EXEC engine the process is running.

Keep in mind that the workaround is to launch the sub-process MODEL not the PARENT as a standalone process, meaning it will run on its own without a parent.

Below link might help you
forum.appian.com/.../e-112742

@sikhivahans, @ajinkyab277, Thank you for the inputs. @Eduardo, That was very useful information. Thanks everyone.