Main process not continuing after sub-process completion (intermittent issue)

RE: Main process not continuing after sub-process completion (intermittent issue)

Shubham Aware — Mon, 02 Feb 2026 13:58:18 GMT

Process instance state becomes too large, causing silent failure after sub-process completion.
Best Practices to Avoid This Issue:
Nullify large PVs after use (set to null when no longer needed).
Divide long processes into smaller sub-processes.
Use async sub-processes where possible.
Use database-driven user input tasks instead of process-driven forms (reduces memory and improves performance)
Avoid long-running process instances - chain processes instead.
I would say proper process design + data management = fewer engine issues.

RE: Main process not continuing after sub-process completion (intermittent issue)

Stefan Helzle — Sun, 01 Feb 2026 10:21:32 GMT

This feels like you directly copied the business BPMN process into Appian, which is a bad idea. These typically show the whole end-to-end process in a single picture, which leads to long running process instances in Appian and an overall inflexible design.

Try to turn that process into smaller chunks where the first starts the next. Pass only the primary key of the main record to avoid dependencies.

Make sure that user input tasks can be completed within max 3 days.

RE: Main process not continuing after sub-process completion (intermittent issue)

vinodn3917 — Fri, 30 Jan 2026 15:40:00 GMT

In Appian,very long-running and complex process models can intermittently fail to resume after sub-process completion due to execution state persistence limits. The recommended approach is to minimize process state, reduce node count, and design shorter, event-driven processes.

RE: Main process not continuing after sub-process completion (intermittent issue)

isabelm780760 — Fri, 30 Jan 2026 15:35:21 GMT

This it's the parent process:

And the completed subprocess: