You are currently reviewing an older revision of this page.

DRAFT KB-XXXX Activity chain not working as expected

Symptoms

User does not see subsequent task even when the tasks are activity chained.

The task is seen in the users tasks list instead.

Cause

The number of unattended nodes that exists between two (attended) activity-chained tasks surpasses the (default) maximum number of 50.

This can be confirmed by navigating to APPIAN_HOME/logs/db_PX** log and checking for entries of the following type:

[Activity Chaining] Could not chain to attended activity. Limit of 50 unattended nodes executed was reached.

Other reasons why an activity chain might break are described in this documentation.

Action

Adding an attended activity with a simple form that says 'Click to continue' is one possible way to avoid hitting this limit.

Your application administrator can also raise the limit setting in a custom.properties file. See also: Configuring Process Execution Properties. However raising this limit is not a suggested approach since this can lead to a perception that the application performance is slow.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2018