This KBA covers what to check/appropriate actions for if a client reports the following error in the Materiality Assessment task of an OGS journey:
The error message suggests that the Batch ID being used is intended for ODS and not OGS journeys.
The first thing to check is the client’s Ongoing Screening journey schema. It should resemble the following flow as per the documentation:
Specifically, check that the client’s schema does not include an ‘Initiate Screening’ task.
If this task type is present in an OGS schema (as above), the observed error can be encountered.
The Initiate Screening task type is intended for ODS only. It is redundant in an OGS journey because the screening initiation is done by the screening provider following the nightly hit identification process.
The batch ID to be used in an OGS journey is assigned when the Materiality Assessment task is opened. Normally this would not be significant.
However, if the schema has been set up incorrectly (with an Initiate Screening task), the batch ID used could be taken from the provider (OGS) or from that task (ODS). Which ID is taken is random because it was never intended for that task to be configured in an OGS schema.
If this is the root cause, the client would have to re-screen in a future ODS to resolve any hits that may have come up.