|Applies To||RSA Product Set: Identity Governance and Lifecycle|
RSA Version/Condition: 6.9.1, 7.0.0, 7.0.1
Product Name: RSA Identity Governance and Lifecycle
|Issue||The Access Fulfillment Express (AFX) fulfilment workflow nodes do not progress either to automated or manual fulfillment. The node is stuck with the following state.|
Workflow flagged as stalled based on stall detection settings
The /home/oracle/AFX/mule/logs/mule.AFX-MAIN.log shows an error result. Any non-zero result other than returning: 0 -> Success indicates the AFX fulfillment failed.
2016-10-21 07:15:46.084 [INFO] org.mule.api.processor.LoggerMessageProcessor:197 - returning: 1 -> Error
|Cause||It is anticipated that some AFX requests may fail, (for a variety of reasons, and the AFX workflow model accommodates for that by allowing the AFX request to return an status code and allows the AFX workflow to consume the status message as either a success or a failure. On a successful result, the AFX workflow should proceed with the provisioning event marked as complete. On an error result, the workflow should also proceed; but on a different workflow path that typically includes generating a manual fulfillment request, or some other error handling path. |
The following versions and patches have a defect that prevents the Workflow engine from correctly interpreting the AFX error response.
If the AFX request returns a successful result the workflow will continue, but if the AFX request returns any non-zero error status, the status is not interpreted correctly and the workflow stalls. If there is an alternate workflow path for manual fulfillment or error handling the workflow does not proceed to this node. Note that the entire workflow is stalled so no further processing occurs.
|Resolution||This issue is resolved in the following versions and patches.|
|Workaround||If the expectation is that this workflow node should always fail and proceed to manual fulfillment for all use cases, then you can modify the workflow to remove the AFX fulfillment node.|
|Notes||This solution does not discuss the many possible ways the AFX fulfillment process might return a non-zero failure result code. If the failure is unexpected, this failure must be investigated separately.|