Problem
After the RP Launchpad task creates IDV sub-journeys, users cannot see those journeys in the Launchpad panel. In some cases the launched journey URL contains a null GUID (00000000-0000-0000-0000-000000000000) instead of a real journey ID.
Symptoms
The Launchpad task completes and entities in scope for IDV are listed, but the IDV mini-journeys do not appear in the side panel.
Clicking a launched journey opens a URL ending in
/journey/00000000-0000-0000-0000-000000000000.The issue is consistent for a specific business-related Access Layer that exists on the entity but is not configured at the journey level.
Root Cause
When the RP Launchpad task creates journeys, it reassigns the Access Layers from the entity draft to the newly created journeys. If the tenant's Security Configuration does not have a Journey Access Layer that matches the Entity Access Layer (geographic or business-related), the system cannot resolve the journey for that user and it becomes invisible.
This is expected platform behaviour. The Access Layer mapping must exist on both the entity and the journey side.