Which of the following is a sign that an application’s performance is degrading and should be addressed with changes to the application design?

A low completion percentage for frequently executed process models is a strong indicator of a design-related performance issue. It means that a significant number of process instances are starting but not finishing, remaining active in the system's memory. These lingering instances consume server resources, and as their numbers grow, they can lead to system-wide performance degradation. This problem is typically caused by design flaws such as unhandled exceptions, logic errors that lead to infinite loops, or poorly designed user tasks that are frequently abandoned. Rectifying this requires analyzing and redesigning the process models to ensure they run to completion efficiently.

A. An HTTP 500 status code indicates an "Internal Server Error" on the external system being called, not a performance issue originating from the Appian application's design.

C. An increase in the number of assigned tasks suggests higher user adoption or workload, which is a measure of usage, not an inherent sign of performance degradation.

D. An increase in the number of application objects reflects the application's growth and complexity, not a direct indicator of a performance problem. A well-designed application can scale to many objects.

1. Appian Documentation

Process Model Metrics: The "Process Model Metrics" page in the official Appian documentation explains the significance of the completion rate. It states

"A low completion rate could indicate that users are abandoning the process

or that the process is frequently paused by exception." Both scenarios point to design flaws that need to be addressed. (See: Appian 23.4 Documentation

"Monitor" section

"Process Model Metrics" page).

2. Appian Documentation

Process and Report Performance: This documentation highlights factors affecting performance. The number of active processes directly impacts memory usage. A low completion rate in high-volume models leads to a rapid accumulation of active processes

which is a primary cause of performance degradation. (See: Appian 23.4 Documentation

"Appian Administration" section

"Process and Report Performance" page).

3. Appian Documentation

Integration Object: The documentation on integrations clarifies that HTTP status codes in the 5xx range represent server-side errors from the system being integrated with

confirming that this is an external issue. (See: Appian 23.4 Documentation

"Design Objects" section

"Integration Object" page

"HTTP Status Codes" subsection).