--- title: PingOne Protect Result node description: Configure the PingOne Protect Result node to update the risk evaluation configuration or completion status of a PingOne Protect risk evaluation in progress. component: auth-node-ref version: 8.1 page_id: auth-node-ref:pingone:pingone-protect-result canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/pingone/pingone-protect-result.html llms_txt: https://docs.pingidentity.com/auth-node-ref/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: 2026-09-01T13:00:59Z page_aliases: ["auth-node-pingone-protect-result.adoc"] section_ids: example: Example availability: Availability inputs: Inputs dependencies: Dependencies configuration: Configuration outputs: Outputs callbacks: Callbacks outcomes: Outcomes errors: Errors --- # PingOne Protect Result node The PingOne Protect Result node updates the risk evaluation configuration or modifies the completion status of the resource while the risk evaluation is still in progress. You can check the results of the evaluation in the PingOne admin console by filtering for `Risk Evaluation Updated` event types. ## Example The following example journey leverages PingOne Protect functionality to perform a risk evaluation. ![Example PingOne Protect journey](_images/pingone-protect-example-journey.png)Figure 1. Example PingOne Protect journey * a The [PingOne Protect Initialize node](pingone-protect-initialize.html) instructs the Ping SDK to initialize a PingOne Signals (Protect) SDK with the configured properties. | | | | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | Initialize a PingOne Signals (Protect) SDK as early in the journey as possible, before any user interaction.This enables it to gather sufficient contextual data to make an informed risk evaluation. | In the subsequent nodes, the end user enters their credentials, which are verified against the identity store. * b The [PingOne Protect Evaluation node](pingone-protect-evaluation.html) performs a risk evaluation against a risk policy in PingOne. The example journey continues depending on the outcome: * `High` The journey requests that the user respond to a push notification. * `Medium` or `Low` The risk isn't significant, so no further authentication factors are required. The journey continues to a [PingOne Protect Result node](pingone-protect-result.html) that returns the success result to PingOne. * `Exceeds Score Threshold` The score returned is higher than the configured threshold and is considered too risky to complete successfully. The journey continues to a [PingOne Protect Result node](pingone-protect-result.html) that returns the failed result to PingOne. * `Failure` The risk evaluation could not be completed, so the authentication attempt continues to the Failure node. * `TEMP_EMAIL_MITIGATION` The risk evaluation returned a recommended action regarding the possibility of a temporary email address. The journey continues to an [Inner Tree Evaluator node](../inner-tree-evaluator.html) that requires the user to respond to a push notification. * `BOT_MITIGATION` The risk evaluation returned a recommended action to check for the presence of a human. The journey continues to a [CAPTCHA node](../captcha.html). * `AITM_MITIGATION` The risk evaluation returned a recommended action regarding the possible presence of an adversary-in-the-middle attack. The journey continues to a [PingOne Protect Result node](pingone-protect-result.html) that returns the failed result to PingOne. * `ClientError` The client returned an error when attempting to capture the data to perform a risk evaluation. The journey continues to the Failure node. * c An instance of the [PingOne Protect Result node](pingone-protect-result.html) returns the `Success` result to PingOne to help with analysis and risk policy tuning. * d A second instance of the [PingOne Protect Result node](pingone-protect-result.html) returns the `Failed` result to PingOne to help with analysis and risk policy tuning. | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | | You can broadly observe the risk evaluation results in the [PingOne threat protection dashboard](https://docs.pingidentity.com/pingone/threat_protection_using_pingone_protect/p1_protect_dashboard.html). You can also use an audit to [review specific risk evaluation results](https://docs.pingidentity.com/pingone/threat_protection_using_pingone_protect/p1_protect_reviewing_risk_evaluations.html), including the JSON response from the risk evaluation. | ## Availability | Product | Available? | | ------------------------------------- | ---------- | | PingOne Advanced Identity Cloud | Yes | | PingAM (self-managed) | Yes | | Ping Identity Platform (self-managed) | Yes | | | | | - | ----------------------------------------------------------- | | | You can't use this node inside a [Page node](../page.html). | ## Inputs This node requires that you've initialized PingOne Protect. For example, by using a [PingOne Protect Evaluation node](pingone-protect-evaluation.html) previously in the journey or by initializing it via the Ping SDK within the app itself. ## Dependencies This node requires a PingOne Worker Service configuration so that it can connect to your PingOne instance and send it the necessary data to make risk evaluations as part of the journey. Find more information in [Connect AM to PingOne](https://docs.pingidentity.com/pingam/8.1/integrations/connect-am-to-pingone.html). ## Configuration | Property | Usage | | ----------------- | ------------------------------------------------------------------------------------ | | Completion Status | Report the status of the journey back to PingOne.Choose from:- `FAILED` - `SUCCESS` | ## Outputs This node doesn't change the shared state. ## Callbacks This node doesn't send any callbacks. ## Outcomes Single outcome path. The node attempts to update the PingOne server but continues along the single outcome without confirming the server received the update. ## Errors The node can log the following: * Warnings * `Failed to update Risk Evaluation result.` The node couldn't update the risk evaluation. Check the journey state, worker service configuration, and PingOne availability. * `Failed to update Risk Evaluation result, riskId or workerId not found` The risk ID or worker ID is missing. Check that the PingOne Protect evaluation was initialized and that the required worker service is configured. * Errors * `PingOne Worker not found: worker ID` The configured PingOne Worker Service couldn't be found. Check the worker service ID.