The inSegment(null) condition and Audience can’t be found error in Adobe Journey Optimizer

In Adobe Journey Optimizer, adding an audience to a condition in a journey can fail even when the audience exists, is visible in the UI, and is retrievable through the API. The condition can also display as inSegment(null), and journey publication can fail with an audience validation error. To fix this issue, refresh the audience metadata, recreate the audience condition, and validate the journey before publication.

Description description

Environment

  • Product: Adobe Journey Optimizer
  • Number of audiences: over 5000 (noted as exceeding recommended guardrails)

Issue/Symptoms

  • A condition based on an existing audience displays as inAudience(null).
  • The intended audience cannot be selected or referenced in the journey condition node.
  • Saving or publishing the journey fails with ERR_AUTHORING_SEGMENTS_3 - Audience can’t be found. It might have been deleted or will be valid in 5 min after the creation.

Resolution resolution

To fix this issue, follow these steps:

  1. Open the affected audience in Adobe Experience Platform.
  2. Make a minor change to the audience description and save the audience.
  3. Return to Adobe Journey Optimizer and open the draft journey.
  4. Remove the existing reference to the affected audience from the condition node.
  5. Recreate the condition and select the intended audience again.
  6. Save the branch and then save the journey.
  7. Reopen the condition node and confirm that it references a valid audience instead of inAudience(null).
  8. Run journey validation or simulation before launch.
  9. Verify that the journey uses the audience without generating errors.

Notes

  • This behavior occurs because Journey Optimizer relies on a cache of recently updated audiences instead of querying all available audiences directly.
  • The cache contains the most recently updated 5000 audiences.
  • Audiences that are not recently modified might not appear for selection until their metadata is refreshed by an update action such as editing and saving the description.
  • Maintaining a large number of unused audiences can impact performance. Consider regular cleanup according to Adobe Experience Platform guardrails documentation.
recommendation-more-help
experience-cloud-kcs-help-kbarticles