Skip to content
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions src/engage/journeys/v2/event-triggered-journeys-steps.md
Original file line number Diff line number Diff line change
Expand Up @@ -384,8 +384,13 @@ Here's an example of a payload before and after enrichment:

{% endcodeexample %}

> warning "Publish timing for enrichment"
> When you publish a journey with enrichment enabled, Segment starts a job to prepare enrichment.The journey stays in a publishing state until enrichment is available. If the cache isn’t populated within 5 hours, the publish fails. Resolve Data Graph sync or join-ID issues, then publish again.
##### Publish behavior and failures

When you publish, Segment builds the enrichment data it needs. The journey stays in a **Publishing** state while that finishes. If enrichment isn’t ready within 5 hours, the publish fails.

If your publish does fail, first check the Data Graph and your warehouse setup—sync status, join IDs, and entity configuration. Fix any issues, create a new version, and publish again.

If a long warehouse job has since finished, re-publishing may succeed without changes.

### Managing activations

Expand Down