KB-1289 Configuring an exception timer in months causes causes the exception to trigger thousands of years in the future

James Lee — Mon, 25 May 2020 18:00:03 GMT

Current Revision posted to Appian Knowledge Base by James Lee on 5/25/2020 6:00:03 PM

This issue has been resolved in a new Appian version. Please upgrade to the latest version of Appian.

Symptoms

Users have the ability to start nodes after a certain number of minutes/hours/days/months of the previous node completing in a process model.

When configuring a node to start a certain number of months after the previous node completes, one may notice the node never activates and the schedule displays a year far in the future (thousands of years):

Cause

This issue has been reported to the Appian product team. This issue has been addressed via AN-63987 and AN-78881 in Appian version 18.2 GA and later.

Action

Upgrade to the latest version of Appian.

Workaround

To fix this issue for existing models with active process instances, perform the following:

Change the timer to trigger after a certain number of days instead of months (e.g., 180 days instead of 6 months). Save and publish the model
Download and install the Process Management Services shared component.
Using the Process Management Services smart services, build a process model that does the following:
1. Upgrades all processes you specify (by ID) using either the Upgrade Process or Upgrade Process From Version smart services.
2. Cancels all active nodes configured with the problematic timer settings in those processes, using the Cancel All Nodes smart service.
3. Starts all nodes cancelled in the previous step in those processes, using the Start All Nodes smart service.
Run that process model during off-peak hours, as this could put considerable load on the system.

Affected Versions

This article applies to Appian 18.1 and earlier.

Last Reviewed: May 2020

Tags: known issues, process models, application design, fixed issues, processes

KB-1289 Configuring an exception timer in months causes causes the exception to trigger thousands of years in the future

Jordan Horwat — Mon, 23 Jul 2018 14:26:15 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 2:26:15 PM

Symptoms

Users have the ability to start nodes after a certain number of minutes/hours/days/months of the previous node completing in a process model.

Cause

This issue has been reported to the Appian product team. The reference numbers for this issue are AN-63987 and AN-78881.

Action

To fix this issue for existing models with active process instances, perform the following:

Change the timer to trigger after a certain number of days instead of months (e.g., 180 days instead of 6 months). Save and publish the model
Download and install the Process Management Services shared component.
Using the Process Management Services smart services, build a process model that does the following:
1. Upgrades all processes you specify (by ID) using either the Upgrade Process or Upgrade Process From Version smart services.
2. Cancels all active nodes configured with the problematic timer settings in those processes, using the Cancel All Nodes smart service.
3. Starts all nodes cancelled in the previous step in those processes, using the Start All Nodes smart service.
Run that process model during off-peak hours, as this could put considerable load on the system.

Affected Versions

This article applies to Appian 18.1 and earlier.

Last Reviewed: May 2018

Tags: known issues, process models, application design, processes, open issues

KB-1289 Configuring an exception timer in months causes causes the exception to trigger thousands of years in the future

Parmida Borhani — Tue, 15 May 2018 21:31:19 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 5/15/2018 9:31:19 PM

Symptoms

Users have the ability to start nodes after a certain number of minutes/hours/days/months of the previous node completing in a process model.

Cause

This issue has been reported to the Appian product team. The reference numbers for this issue are AN-63987 and AN-78881.

Action

To fix this issue for existing models with active process instances, perform the following:

Change the timer to trigger after a certain number of days instead of months (e.g., 180 days instead of 6 months). Save and publish the model
Download and install the Process Management Services shared component.
Using the Process Management Services smart services, build a process model that does the following:
1. Upgrades all processes you specify (by ID) using either the Upgrade Process or Upgrade Process From Version smart services.
2. Cancels all active nodes configured with the problematic timer settings in those processes, using the Cancel All Nodes smart service.
3. Starts all nodes cancelled in the previous step in those processes, using the Start All Nodes smart service.
Run that process model during off-peak hours, as this could put considerable load on the system.

Affected Versions

This article applies to Appian 18.1 and earlier.

Last Reviewed: May 2018

Tags: known issues, process models, processes, open issues

KB-1289 Configuring an exception timer in months causes causes the exception to trigger thousands of years in the future

Nick Vigilante — Wed, 14 Jun 2017 15:12:36 GMT

Revision 3 posted to Appian Knowledge Base by Nick Vigilante on 6/14/2017 3:12:36 PM

Symptoms

Users have the ability to start nodes after a certain number of minutes/hours/days/months of the previous node completing in a process model.

Cause

This issue has been reported to the Appian product team. The reference numbers for this issue are AN-63987 and AN-78881.

Action

To fix this issue for existing models with active process instances, perform the following:

Change the timer to trigger after a certain number of days instead of months (e.g., 180 days instead of 6 months). Save and publish the model
Download and install the Process Management Services shared component.
Using the Process Management Services smart services, build a process model that does the following:
1. Upgrades all processes you specify (by ID) using either the Upgrade Process or Upgrade Process From Version smart services.
2. Cancels all active nodes configured with the problematic timer settings in those processes, using the Cancel All Nodes smart service.
3. Starts all nodes cancelled in the previous step in those processes, using the Start All Nodes smart service.
Run that process model during off-peak hours, as this could put considerable load on the system.

Tags: known issues, process models, processes, open issues