<@U04S8PLJWMT> in the latest sync i can see number...
# ask-ai
s
@kapa.ai in the latest sync i can see number of records extracted as well as | time elapsed whats the meaning of time elapsed
k
In Airbyte, the "time elapsed" shown in the sync summary represents the total duration it took for the sync to complete, measured from the start to the end of the sync process. This is typically displayed in hours, minutes, and seconds (e.g., 1h 28m 21s). It helps you understand how long the data extraction and loading process took for that particular sync event. For example, if you see: - Number of records extracted: The total records read from the source during the sync. - Time elapsed: The total time (e.g., 38h 18m 26s) it took for the sync to run from start to finish. This information is useful for monitoring performance and identifying potential bottlenecks in your data pipeline. Reviewing the elapsed time alongside the number of records extracted and loaded can help you spot issues or inefficiencies in your syncs. The sync timeline in Airbyte provides these metrics to help you monitor and troubleshoot your connections effectively [Review the Connection Timeline](https://docs.airbyte.com/platform/1.8/cloud/managing-airbyte-cloud/review-connection-timeline#syncs-refreshes-and-clears).
s
@kapa.ai will the ui refresh of airbyte effects the sync in any possible way
k
A message from kapa.ai
Based on the available knowledge sources, there is no explicit information indicating that refreshing the Airbyte UI (such as reloading the browser page) will affect an ongoing sync operation. The documentation focuses on how syncs, refreshes, and clears are managed and how their statuses are tracked, but does not mention any impact from UI actions like page refreshes on the backend sync processes [Syncs, refreshes, and clears](https://docs.airbyte.com/platform/1.8/cloud/managing-airbyte-cloud/review-connection-timeline#syncs-refreshes-and-clears). However, there are references in GitHub issues to UI refresh errors causing inconvenience or errors in the interface, but these are related to the user experience and not to the actual data sync process itself. For example, users have reported errors when refreshing the UI, but there is no mention that this interrupts or affects the underlying sync jobs [Github Issue: Refresh in UI causing error](https://github.com/airbytehq/airbyte/issues/65070). In summary: Refreshing the Airbyte UI does not affect the actual sync process, but may cause temporary UI errors or require you to navigate back to the main page. The sync itself continues to run on the backend.