Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Suggested Answer
+1
person also asked this
people also asked this
Replies
6 replies
Answers
1 answer
Subscribers
11 subscribers
Views
8290 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Error "work Item Cancelled"
francescop389
over 7 years ago
hi all,
have some of you ever faced the alert "ERROR: Work Item Cancelled" (see attached) when a process node goes error?
I'm getting this error twice on a process, in two different Script Tasks which never failed.
Since inside the node there's only a rule, I even tried to evaluate the rule itself using the value form process Variable, and the rule is working fine.
I would like to know the root cause of this error, in order to prevent from having it again. Any suggestions?
thanks
OriginalPostID-267284
Discussion posts and replies are publicly visible
Parents
+1
rajesh kilaru
A Score Level 2
over 5 years ago
Cause
This issue typically occurs when the impacted process is running under a deactivated user account. Due to this, a permissions check fails when trying to execute certain nodes, for example, User Input Tasks and some unattended activities. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-46187.
Action
If the error is occurring in a sub-process, ensure that the sub-process node in the parent process is not set to run as the deactivated user. For example, if the parent process was designed by a deactivated user, set it to run as the initiator. If the parent process was initiated by a deactivated user, set the sub-process to run as the process designer.
If the error is occurring in an unattended activity, repeat the steps from the above on the "Assignment" tab of the failing unattended activities of the Process Model.
If the error is occurring in an User Input Task or another attended activity, ensure that the user is not referenced in the assignment of that node, cancel all pending activity on the model, and restart the node as an active user.
Workaround
If all of the steps in the "Workaround" section fail to resolve the issue, temporarily reactivate the deactivated user account and add the user to a group, then remove the user from the group before allowing the process to complete. In order to ensure the deactivated account cannot be accessed by the user who it belonged to, follow the steps below:
Change the e-mail address to something other than the user's actual e-mail address.
Reset the password via the Admin Console.
Affected Versions
This applies to all versions of Appian.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Reject Answer
Cancel
Reply
+1
rajesh kilaru
A Score Level 2
over 5 years ago
Cause
This issue typically occurs when the impacted process is running under a deactivated user account. Due to this, a permissions check fails when trying to execute certain nodes, for example, User Input Tasks and some unattended activities. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-46187.
Action
If the error is occurring in a sub-process, ensure that the sub-process node in the parent process is not set to run as the deactivated user. For example, if the parent process was designed by a deactivated user, set it to run as the initiator. If the parent process was initiated by a deactivated user, set the sub-process to run as the process designer.
If the error is occurring in an unattended activity, repeat the steps from the above on the "Assignment" tab of the failing unattended activities of the Process Model.
If the error is occurring in an User Input Task or another attended activity, ensure that the user is not referenced in the assignment of that node, cancel all pending activity on the model, and restart the node as an active user.
Workaround
If all of the steps in the "Workaround" section fail to resolve the issue, temporarily reactivate the deactivated user account and add the user to a group, then remove the user from the group before allowing the process to complete. In order to ensure the deactivated account cannot be accessed by the user who it belonged to, follow the steps below:
Change the e-mail address to something other than the user's actual e-mail address.
Reset the password via the Admin Console.
Affected Versions
This applies to all versions of Appian.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Reject Answer
Cancel
Children
No Data