Skip to main content
Solved

Why does the Journey interface show tasks as completed even though the backend data or workflow status is still processing?

  • January 8, 2026
  • 1 reply
  • 2 views
J

Users may notice situations where a Journey task appears as “Completed” in the UI, yet backend data updates or related operations are still pending. This discrepancy usually happens when the UI is showing a cached version of the task state that hasn’t been refreshed to reflect updates from the Journey Logic Engine. In many cases, the task may have been auto-completed by system rules in the background, or the user session may have loaded an outdated snapshot of the task list before the backend finished processing.

Best answer by jawadkhan

This mismatch occurs when the UI’s cached state doesn’t reflect the backend status from the Journey Logic Engine.

Common scenarios:

  • Background autocompletion rules completed the task server-side.
  • The UI did not refresh after backend updates or merge events.
  • The user session loaded an outdated snapshot of the task list.

To fix:

  • Enable real-time task polling in Journey settings or re-query using the Journey Query API (GET /journeyquery/api/journey-instance/{id}/task/{taskId}). 
  • Clear client-side cache and refresh the Journey dashboard (Ctrl + F5 in browser).
  • Check Autocompletion Audit for system-triggered task completions — "CompletedBy": "System" indicates background automation.

Note

In multi-user setups, different users may see different cached states until the next refresh or polling cycle. Always refresh the dashboard after bulk or automated task updates.

1 reply

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

This mismatch occurs when the UI’s cached state doesn’t reflect the backend status from the Journey Logic Engine.

Common scenarios:

  • Background autocompletion rules completed the task server-side.
  • The UI did not refresh after backend updates or merge events.
  • The user session loaded an outdated snapshot of the task list.

To fix:

  • Enable real-time task polling in Journey settings or re-query using the Journey Query API (GET /journeyquery/api/journey-instance/{id}/task/{taskId}). 
  • Clear client-side cache and refresh the Journey dashboard (Ctrl + F5 in browser).
  • Check Autocompletion Audit for system-triggered task completions — "CompletedBy": "System" indicates background automation.

Note

In multi-user setups, different users may see different cached states until the next refresh or polling cycle. Always refresh the dashboard after bulk or automated task updates.

Terms & ConditionsCookie settingsAccessibility statement