Subprocess

RE: Subprocess

rodneyb008718 — Wed, 25 Feb 2026 08:41:32 GMT

In high-volume architectures have you seen better results leaning toward asynchronous process models with data persistence instead of relying on PV handoffs?

bitlife

RE: Subprocess

AlmudenaMM — Mon, 07 Oct 2019 06:21:55 GMT

Thank you very much for your answer

RE: Subprocess

davel001150 — Fri, 04 Oct 2019 19:32:46 GMT

If by threads, you mean Execution engines, you will want to avoid Subprocess altogether. Each sub-process runs on the same execution-analytics pair as the parent process. This is why a recommended practice according to Appian engineers I've spoken with is to limit processes that spawn large numbers of subprocesses.

a!startProcess and Start Process smart service are better options because they can be executed on a different engine, but they aren't always viable because they can't return PV's to the parent process.

Starting processes via messaging may seem like a viable alternative, but the messaging carries with it so much overhead that it didn't get any recommendations. The general consensus, as I gathered, was to avoid messaging where possible.

RE: Subprocess

Sikandar — Fri, 04 Oct 2019 17:48:31 GMT

Refer below link it should give you some insight

https://docs.appian.com/suite/help/19.3/Ways_to_Start_a_Process_From_a_Process.html

RE: Subprocess

Mike Schmitt — Fri, 04 Oct 2019 14:04:49 GMT

Can you tell us a bit more detail about your use case?