In some cases, users notice that after an Event Ingress is processed successfully, the Journey task does not reflect updated data in one or more entity fields. This can be confusing, the event appears to have triggered correctly, but the underlying entity (for example, Client or Product) remains unchanged. Understanding how Fenergo applies updates through Event Ingress and field scoping in Journeys can help diagnose why these updates are silently ignored or skipped.
Solved
Why is my Journey task not updating the expected entity field after an Event Ingress, even though the event was successfully received?
Best answer by jawadkhan
This typically happens when the Event Ingress payload and the Journey field scoping configuration are not aligned.
In Fenergo, Event Ingress applies updates according to:
- The field category and target entity defined in Policy.
- The merge strategy defined by the Event type (overwrite, append, or ignore behaviour).
- Whether the Journey allows updates to verified vs draft data.
- If a field is out of scope for the event or mapped to a different entity context (e.g., Product vs Client), the update is silently ignored.
To fix this:
- Ensure the Event Ingress payload includes only fields configured under the correct category and Target Entity (as per Policy).
- Confirm the merge strategy in Integration Hub matches the expected behaviour (e.g., “overwrite existing values”).
- Re-run the ingestion and check the Event Notifications feed - it will include messages identifying skipped or rejected fields.
Best Practice
Keep merge rules simple - use one merge strategy per entity type (Client, Product, Related Party). Align Event Ingress configuration with Policy field scoping to avoid mismatched updates.
This typically happens when the Event Ingress payload and the Journey field scoping configuration are not aligned.
In Fenergo, Event Ingress applies updates according to:
- The field category and target entity defined in Policy.
- The merge strategy defined by the Event type (overwrite, append, or ignore behaviour).
- Whether the Journey allows updates to verified vs draft data.
- If a field is out of scope for the event or mapped to a different entity context (e.g., Product vs Client), the update is silently ignored.
To fix this:
- Ensure the Event Ingress payload includes only fields configured under the correct category and Target Entity (as per Policy).
- Confirm the merge strategy in Integration Hub matches the expected behaviour (e.g., “overwrite existing values”).
- Re-run the ingestion and check the Event Notifications feed - it will include messages identifying skipped or rejected fields.
Best Practice
Keep merge rules simple - use one merge strategy per entity type (Client, Product, Related Party). Align Event Ingress configuration with Policy field scoping to avoid mismatched updates.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.