Identifying Data Service Failures
A Data Service can fail due to a variety of reasons. A failure can be caused by data errors such as: wrong formatting, service outages, connection issues that may or may not have a known cause. If the Evaluation Summary shows a Partial Result, it means that there was a data service failure. When the user hovers over the Partial result, you can see that the evaluation exited the workflow.
Navigating down to the Data Sources section should show a ‘red x’ indicator noting failed data service. Clicking on the failed data service node will open up the Raw Response for that data service, potentially showing us why it failed.
You can check the Raw Response for helpful information. In the example below, the wrong email format caused the failure i.e. ‘.con’ instead of ‘.com’. Rerunning the evaluation with a legal email domain will correct the issue in this case.
Understanding Service Failure Handling
It can also be helpful to understand how your workflow handles service failures. To check this, close the Raw Response box and click on the workflow link found at the top of the Evaluation Summary Page.
This will take you to the workflow used to decision the evaluation.
In the previous example, Socure 30 failed to process due to an invalid email address being used. Clicking on the Socure 30 data service node and then Options menu will expose this data service’s Service Failure Handling option. In this case, it is set to the default “Exit Workflow” option. This means the workflow will stop processing the evaluation and abort when the required data is not properly transmitted between the data service and Alloy.
The default Service Failure Handling setting for the workflow is set to exit during a service failure. This setting can be adjusted based on the preference for a given data service node or tag node, but we generally recommend exiting the workflow.
Article is closed for comments.