Users may notice that Related Party tasks show stale or incomplete details, even when the Related Party record or its associations have recently changed in another Journey, through an API update, or via an ETL process. This occurs because Related Party tasks in Fenergo display a snapshot of data captured at the moment the task was first opened. Any updates made outside the active Journey context are not automatically reflected until the task is refreshed or reinitialized.
Solved
Why do Related Party tasks sometimes display outdated or missing information, even though the underlying data has been updated elsewhere?
Best answer by jawadkhan
Related Party tasks display snapshot data captured when the task instance was opened. If entity or association data changes outside the active Journey (e.g., via API, ETL, or another Journey), the task will not automatically refresh.
To resolve:
- Confirm whether the Related Parties or Related Party Data & Documents task is configured for live refresh in Journey Builder.
- If not, trigger a task reinitialization by reopening the task or refreshing the Journey.
- For cross-journey conflicts, use the Conflict Resolution or Proposed Changes task to synchronize updates.
Known Pattern
In large Journeys with multiple nested entities, child relationships may appear stale until the parent hierarchy is re-synced. Schedule periodic refreshes or configure Conflict Resolution to automatically flag differences.
Related Party tasks display snapshot data captured when the task instance was opened. If entity or association data changes outside the active Journey (e.g., via API, ETL, or another Journey), the task will not automatically refresh.
To resolve:
- Confirm whether the Related Parties or Related Party Data & Documents task is configured for live refresh in Journey Builder.
- If not, trigger a task reinitialization by reopening the task or refreshing the Journey.
- For cross-journey conflicts, use the Conflict Resolution or Proposed Changes task to synchronize updates.
Known Pattern
In large Journeys with multiple nested entities, child relationships may appear stale until the parent hierarchy is re-synced. Schedule periodic refreshes or configure Conflict Resolution to automatically flag differences.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.