Validate Existing Reference Data Values

Journey administrators can now enable validation of existing reference data values within a journey, so that values selected under an earlier version of a Lookup or Lookup Link — or brought in through migration or data ingest — are checked against the current configuration and must be updated before a user can proceed. This keeps captured data current and helps ensure that only valid, current values are passed to downstream systems.

The new toggle, "Validate existing Reference Data values", is available in the Journey Configuration drawer in Journey Builder. It is disabled by default and applies tenant-wide; when enabled it applies to all standard journey contexts where draft data is saved, across both the user interface and the API, and takes effect on new and existing journeys the next time a task is triggered or data is saved.

When enabled, existing values in supported fields — Select Dropdown, Multiple Select Dropdown, and current (V2) Linked Select Dropdown and Linked Multiple Select Dropdown — are validated when a task loads and again when a task is saved or completed. Invalid values are shown in an error state in the user interface, with toast messages on save or complete, including invalid values held within data groups. Only fields that are editable and visible in context are validated, so users are never blocked by values they cannot see or change.

This setting should only be enabled when all Lookup Link configuration uses the current (V2) model, as Legacy (V1) Lookup Links are not supported.

Permissions Impacted

No permissions are impacted. Managing the setting reuses the existing Journey Configuration Edit permission, and no new permission is introduced.

User Guide Reference: Configuring Journeys