Overview
Ongoing Screening (OGS) journeys do not trigger after LexisNexis confirms that the batch search has completed successfully. Despite the confirmation email, OGS journeys do not initiate as expected.
Investigation and Findings
Configurations checked: All configurations were reviewed and no misconfigurations were found.
Triggering mechanism identified: The root cause was traced to the Launchpad trigger, which was incorrectly placed under the Materiality Assessment task type instead of a Data Task.
Resolution
Move the Launchpad trigger from the Materiality Assessment task type to a Data Task. Once the trigger is associated with a Data Task, OGS journeys will initiate correctly.
Verification Steps
Confirm receipt of the batch search completion email from LexisNexis.
Navigate to the journey configuration and verify the Launchpad trigger is associated with a Data Task, not a Materiality Assessment task.
Re-trigger the OGS batch and confirm that journeys are now initiated.
Root Cause
The Launchpad trigger was configured under the Materiality Assessment task type. This task type does not support OGS journey initiation. Placing the trigger under a Data Task resolves the issue.