Skip to main content
Solved

Why don’t updates from external systems appear immediately in Fenergo after an Event Ingress or data import?

  • January 8, 2026
  • 1 reply
  • 2 views

Users often expect that once an external system sends updated entity data to Fenergo, those changes should appear instantly in the UI or Journey context. However, Event Ingress and other integration workflows in Fenergo are asynchronous by design. When an event is received, the API returns a 202 Accepted response to confirm successful receipt — but the actual update occurs later, after the event has completed internal processing and passed validation. As a result, updates only become visible once the workflow finishes and a success notification is generated.

Best answer by jawadkhan

Event Ingress is asynchronous — an accepted event is queued for internal processing. Updates will appear only after the full workflow completes and a success notification is emitted. ²

Check

  • The Event Queue Monitor in Integration Hub for pending or retrying events.
  • That the eventType / eventSubtype (e.g. externaldata:dataimport or verifiedimport:updateentity) is configured correctly for your tenant.
  • That the event ran under a service user with permission to update the target entity.

Tip

  • For near real-time updates, configure Integration Hub Event Flows with “Run Mode: Sync” or “Wait for Response”.
  • For high-volume imports, schedule DataImport mini-batches to balance throughput and latency.

1 reply

Forum|alt.badge.img
  • Community Manager
  • Answer
  • January 15, 2026

Event Ingress is asynchronous — an accepted event is queued for internal processing. Updates will appear only after the full workflow completes and a success notification is emitted. ²

Check

  • The Event Queue Monitor in Integration Hub for pending or retrying events.
  • That the eventType / eventSubtype (e.g. externaldata:dataimport or verifiedimport:updateentity) is configured correctly for your tenant.
  • That the event ran under a service user with permission to update the target entity.

Tip

  • For near real-time updates, configure Integration Hub Event Flows with “Run Mode: Sync” or “Wait for Response”.
  • For high-volume imports, schedule DataImport mini-batches to balance throughput and latency.