AWF Transition Incomplete
We're currently using 6.6 P2. We've encountered a situation where a user action will execute and the downstream update content nodes will execute, but the AWF process will not continue to the next logical user action or stop node. It basically completes the update content actions and then clocks. Even on a stop node the status remains running instead of complete. Has anyone encountered this or know of a solution?
William, do all the nodes in AWF are connected in a complete path?
I have seen situations like yours where there was a group of nodes that where completely independent from the overall workflow.
I've only seen this happen once (on 6.9 SP1 P3). I used the AWF Job Troubleshooter and restarted the workflow. Everything the last user click did was undone (even the nodes that showed as complete). The user was able to click the same action again and it worked properly. We chalked it up to an anomaly and decided not to report it unless the issue repeats.
The AWF process had been working properly until I consolidated a number of update content nodes that were downstream from various user action nodes. I didn't change any endpoints, though, and it looks like all transitions still flow to a defined stop node.
Three items I can think of to check:
1) If a notification node is downstream of the Update node (or any node for that matter) there are a few items to check. Any of these missing will cause AWF to halt on the node just before the Notification node. The Notification nodes leverage the existing email function on the application via an API call.
a) You must make sure that it has a valid email address (so if leveraging afield that field MUST be populated) in one of the To: fields or AWF will just stop. I generally add a Requirement DDE or leverage a Rule on the Transition leading to that notification node.
b) Also you need to make sure that users have the Email option in the Access Role for that application.
c) Notifications must be turned on for the application.
2) If you are trying to update (or Evaluate) a field it MUST be on layout. If it isn't AWF may pause as it can't execute the update so unless you have the node set to Always Succeed it won't move forward. I've started adding a hidden Admin section or tab set to handle fields that are touched by AWF (evals/updates) so that they can be on layout.
3) Go into a record in AWF Troubleshooter and under the ellipsis (...) next to Save button, there is an option to Check Syntax, that will let you know if there any issues AWF can find. I think 6.6 has this function, but I don't have that version available to me to verify. 6.7 and above does.
Hope that helps.
I ran the the syntax check, which returned multiple errors of "A loop exists that does not contain a transition marked as upstream. Node XXXXX:XXXX is contained in this loop." Is there a simple way to translate the node ID to the node name for easier identification? Thanks.
The AWF Troubleshooter should be helpful here. Click on "Show Active Nodes Only" and you'll be able to see where you are in the workflow. The node numbers show in the troubleshooter I believe, so you can compare the number to nodes around where it stopped to locate the one that's in error.