The process model completion rate is the percentage of instances that have successfully finished. A low rate of 10% indicates that 90% of instances are not completing.

Option A is correct because if a process is designed to be long-running but the archival policy is set to a shorter duration, instances will be archived before they can finish. Archived processes are not considered "completed," thus directly lowering the completion rate.

Option B is correct because instances that encounter an error are paused and enter an exception state. These paused instances are not "completed." If a large number of these errors are not resolved, they will accumulate, significantly reducing the overall completion rate.

C. A large value for archival days gives processes more time to complete, which would likely increase, not decrease, the completion rate.

D. The number of nodes does not directly determine the completion rate; a complex process can still have a 100% completion rate if designed correctly.

1. Appian Documentation

Process Model Metrics: The "Completion" metric is defined as the percentage of process instances that completed. Instances that are active

paused by exception

or canceled are considered "Not Completed." This supports the reasoning that paused (errored) processes (Option B) lower the completion rate.

Source: Appian 23.4 Documentation

"Process Model Metrics" section.

2. Appian Documentation

Archiving Processes: "Archived or deleted processes are not included in process reports..." and "If a process is archived before it is completed

it will never be completed." This directly supports the reasoning that premature archival due to a short archival period for long-lived processes (Option A) causes a low completion rate.

Source: Appian 23.4 Documentation

"Data Management" page

"Archiving Processes" section.