Skip to main content
April 22, 2026
Question

Process Model- split using AND gate

  • April 22, 2026
  • 7 replies
  • 0 views

Hi Community,

Let’s say I have 15 nodes in a process model.

Scenario 1: The nodes are placed linearly and execute one after another.

Scenario 2: The nodes are split into 5 branches, with 3 nodes in each branch, using an AND/OR gate.

On testing above scenarios, when I config this inside startprocess and try to trigger it from web API, both scenarios are taking approx same time. Does appian on the backend still executes it linear irrespective of how we branch it in single process model canvas?

7 replies

stefanhelzle0001
April 22, 2026

The process follows the logic, but the individual nodes are enqueued and executed by one of the multiple execution engines.

Is this just out of curiosity, or do you have the need to speed up things?

April 22, 2026

I wanted to speed up things

stefanhelzle0001
April 22, 2026

Do you want to, or do you have to?

Did you try activity chaining?

shubhama926776
April 22, 2026

AFAIK, Appian does run one process instance on one execution engine - so even with AND parallel branches, all nodes are processed by that single engine, meaning:
True thread-level parallelism doesn't happen within one instance
Branches are queued and picked up by the same engine serially.
The parallel in AND gateway is logical, not true concurrent threading within a single instance.

True speedup only via background startprocess() - each gets its own engine instance.

April 22, 2026

Okay, Thanks .

varuntejg243705
April 23, 2026

Short answer: No, Appian does NOT force everything to run linearly.

Appian does support parallel execution with gateways, but it doesn’t guarantee simultaneous execution.

Appian process execution engine uses a limited thread pool, so parallel branches are scheduled based on available resources.

In your case, as the nodes are lightweight, both linear and parallel flows take similar time. You’ll see real performance improvement only when each branch has heavy operations like integrations or long-running tasks.