KB-1637 Activity chaining not working as expected

Parmida Borhani — Wed, 08 Aug 2018 02:17:30 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 8/8/2018 2:17:30 AM

Symptoms

A user does not see the 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 the <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' between the two chained tasks is one possible way to avoid hitting this limit.
Consider redesigning the process since having more than 50 unattended nodes in between two chained tasks can lead to poor user experience.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, application design

DRAFT KB-XXXX Activity chain not working as expected

Tejas Kargutkar — Tue, 07 Aug 2018 14:27:42 GMT

Revision 11 posted to Appian Knowledge Base by Tejas Kargutkar on 8/7/2018 2:27:42 PM

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' between the two chained tasks is one possible way to avoid hitting this limit.
Consider redesigning the process since having more than 50 unattended nodes in between two chained tasks can lead to poor user experience.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2018

Tags: engines, application design, Activity Chaining

DRAFT KB-XXXX Activity chain not working as expected

Tejas Kargutkar — Tue, 07 Aug 2018 14:27:22 GMT

Revision 10 posted to Appian Knowledge Base by Tejas Kargutkar on 8/7/2018 2:27:22 PM

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' between the two chained tasks is one possible way to avoid hitting this limit.
Consider redesigning the process since having more than 50 unattended nodes can lead to poor user experience.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2018

Tags: engines, application design, Activity Chaining

DRAFT KB-XXXX Activity chain not working as expected

Tejas Kargutkar — Thu, 02 Aug 2018 10:41:03 GMT

Revision 9 posted to Appian Knowledge Base by Tejas Kargutkar on 8/2/2018 10:41:03 AM

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' between the two chained tasks is one possible way to avoid hitting this limit.
The chained execution node limit can be increased. See Configuring Process Execution Properties for more details". Please note that increasing this limit is not supported on Appian Cloud.
- WARNING: Raising this limit is not recommended since it can contribute to performance degradation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2018

Tags: engines, application design, Activity Chaining

DRAFT KB-XXXX Activity chain not working as expected

Tejas Kargutkar — Thu, 02 Aug 2018 10:37:13 GMT

Revision 8 posted to Appian Knowledge Base by Tejas Kargutkar on 8/2/2018 10:37:13 AM

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' between the two chained tasks is one possible way to avoid hitting this limit.
The chained execution node limit can be increased. See Configuring Process Execution Properties for more details"
- WARNING: Raising this limit is not recommended since it can contribute to performance degradation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2018

Tags: engines, application design, Activity Chaining

DRAFT KB-XXXX Activity chain not working as expected

Tejas Kargutkar — Wed, 01 Aug 2018 11:47:03 GMT

Revision 7 posted to Appian Knowledge Base by Tejas Kargutkar on 8/1/2018 11:47:03 AM

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.
The chained execution node limit can be increased. See Configuring Process Execution Properties for more details"
- WARNING: Raising this limit is not recommended since it can contribute to performance degradation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2018

Tags: engines, application design, Activity Chaining

DRAFT KB-XXXX Activity chain not working as expected

Tejas Kargutkar — Tue, 31 Jul 2018 12:26:02 GMT

Revision 6 posted to Appian Knowledge Base by Tejas Kargutkar on 7/31/2018 12:26:02 PM

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.

Raising this limit however 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

Tags: engines, application design, Activity Chaining

DRAFT KB-XXXX Activity chain not working as expected

Tejas Kargutkar — Tue, 31 Jul 2018 12:25:26 GMT

Revision 5 posted to Appian Knowledge Base by Tejas Kargutkar on 7/31/2018 12:25:26 PM

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

Tags: engines, application design, Activity Chaining

DRAFT KB-XXXX Activity chain not working as expected

Tejas Kargutkar — Tue, 31 Jul 2018 12:22:20 GMT

Revision 4 posted to Appian Knowledge Base by Tejas Kargutkar on 7/31/2018 12:22:20 PM

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.

You can confirm this by checking the APPIAN_HOME/logs/db_PX** log and check if the following type of entries are seen:

[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

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2018

Tags: engines, application design, Activity Chaining

DRAFT KB-XXXX Activity chain not working as expected

Tejas Kargutkar — Tue, 31 Jul 2018 12:21:58 GMT

Revision 3 posted to Appian Knowledge Base by Tejas Kargutkar on 7/31/2018 12:21:58 PM

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.

You can confirm this by checking the APPIAN_HOME/logs/db_PX** log and check if the following type of entries are seen:

[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

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2018

Tags: engines, application design, Activity Chaining

Activity chain not working as expected

Tejas Kargutkar — Fri, 27 Jul 2018 12:07:02 GMT

Revision 2 posted to Appian Knowledge Base by Tejas Kargutkar on 7/27/2018 12:07:02 PM

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.

You can confirm this by checking the AE_home/logs/db_PX** log and check if the following type of entries are seen:

[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 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

Activity chain not working as expected

Tejas Kargutkar — Thu, 26 Jul 2018 21:55:03 GMT

Revision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 7/26/2018 9:55:03 PM

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.

You can confirm if the number of nodes that exists between two (attended) activity-chained tasks

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