Journey

When working with complex Journeys that involve multiple entities — such as Clients, Products, and Related Parties — it can be difficult to understand how data updates flow between them. Fenergo provides built-in tracing and audit tools that let you see exactly where data changes originate, how they propagate across entities, and which system components (such as API calls, user actions, or Event Ingress events) triggered those updates.

It can be confusing when a Product that appears to have completed its Offboarding process suddenly changes back to “In Review” after another connected Journey starts. In Fenergo, this behaviour occurs because the Product’s state machine is automatically re-evaluated when a new Journey is triggered. If the Product still has open review steps or pending tasks, the platform may interpret it as incomplete and reset the state accordingly.

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.