The Data Pipeline view now shows sync progress as a timeline of saved task states. It names the work currently running, keeps completed work visible, and separates a failed task from a warning or an interrupted connection.
The timeline follows the jobs that make synced data useful: collecting requests, saving and checking them, reconciling spend history, and refreshing conversations and views. A long preparation step can show its own smaller tasks. Work running in parallel appears together in the current-activity area.
See what is moving
Tasks report counts where the worker has them. A progress bar appears when a task reports a positive total; an unknown total stays labeled as unknown. Reaching a count’s total does not mark the task complete while it is still running.
The worker heartbeat and the time since measured progress are shown separately. A heartbeat means the worker has reported that it is alive. The progress timestamp changes when it reports progress in its work. Those two readings help an operator distinguish a connected worker from a task whose measured work has stopped advancing.
Keep the result through a reconnect
Reloading the view restores the saved run and its tasks. If the status connection drops, the last received states remain visible with an interruption notice while the browser retries. Starting another sync labels the previous run as saved until details of the new one arrive.
Optional work that fails appears as a warning, while required work that fails makes the run fail. Skipped tasks keep their reason. The diagnostic console remains available for the underlying messages, but its text no longer determines which task is complete.
Open Operations → Data Pipeline in a workspace to follow its latest run. The timeline describes sync activity; it does not estimate when the entire run will finish.
Development record: November 5–6, 2026. Written retrospectively; these dates describe development, not the first release.