Skip to main content
sivak0197
June 14, 2026
Question

Process Model (Sub processes are not starting)

  • June 14, 2026
  • 5 replies
  • 0 views

I have a question regarding the subprocess status shown in the attached screenshot.

The subprocesses are displaying the status as "Unattended" instead of "Completed". I have configured the subprocess node to "Run as whoever designed the process model" in the assignment settings.

Could you please help me understand why the subprocesses are still showing as Unattended rather than Completed?

I've attached the screenshot for reference.

5 replies

shubhama926776
June 15, 2026

Run as designer only controls permissions, not the node type. A subprocess stays Unattended while active and turns Completed only when its instance reaches a valid end node, so yours is likely still running or stuck on an internal node.

harshas2775
June 15, 2026

Once the subprocess completes by reaching an end node you should see the status as Completed. Inspect your subprocess instances if they have any errors or is paused at a node or is still in progress! 

July 13, 2026

I absolutely enjoy this conversation! I was lately having trouble getting my sub-processes to trigger in Appian and felt I was losing my wits. It turned out that I had overlooked a simple setting! Thank you for sharing your solutions; learning scratch games from other people's experiences is quite beneficial. 

July 15, 2026

The "Run as whoever designed the process model" option only specifies the execution permissions for the subprocess; it doesn't affect its status. A subprocess remains in the Unattended state while it is executing without user interaction and changes to Completed only after it successfully reaches an end node. If it's still showing Unattended, check the subprocess instance to see if it's still running, waiting at a node, paused, or has encountered an error.

July 21, 2026

Thank you, @suresh0905. I had mistakenly assumed it would influence whether the instance appeared as hot games Completed. I'll inspect the subprocess instance to determine whether it's still waiting at a node, paused, or encountering an issue before reaching the end node. I really appreciate your clear and practical guidance—it pointed me in the right direction.