Summary
This article explains an issue where the Verify Entity task is incorrectly configured within a Data Deletion journey, resulting in unintended offboarding being triggered for other jurisdictions. It also provides guidance on how to correctly configure the journey to avoid this outcome.
Issue Description
The issue occurs when the Verify Entity task is used as part of a Data Deletion journey. This configuration is not appropriate because Data Deletion journeys should only focus on removing a specific jurisdiction. Once a jurisdiction is deleted, it should no longer be considered in scope.
However, using Verify Entity within this workflow can cause other jurisdictions to be evaluated incorrectly, leading to unintended offboarding.
Root Cause
Using Verify Entity within a Data Deletion journey causes jurisdiction removal to be interpreted as a signal to start offboarding. This behavior is expected for verification workflows but not for deletion workflows.
Recommended Solution
To prevent unintended offboarding:
Avoid using the Verify Entity task in any Data Deletion journey.
Review the journey configuration to ensure that jurisdiction removal actions do not trigger the offboarding logic.
Ensure that Data Deletion journeys are designed to affect only the jurisdiction being deleted, without initiating validation or verification steps meant for broader compliance workflows.