3747723 - Different running times when comparing a Replication Flow "Run Details" and "Metrics tab"

Upon analyzing the running time of a given Replication Flow, a discrepancy in the total duration time of the same job can be seen when comparing "Run Details" and the "Metrics" tab, as per the example in the below image:

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

SAP Datasphere

Working as per system design.

This is not an issue, but by system design.

This discrepancy occurs because SAP Datasphere measures different aspects of job execution timing:
- Run Details timing represents the total elapsed time from when the job was scheduled/queued until completion, including all waiting periods and system overhead.
- Metrics timing shows the actual active data processing time when the replication threads were actively transferring data

Also, according to Monitoring Flows, the Status of the Run Details is updated every 10 minutes (if not ran via task chain). So if the actual replication task (detailed in Metrics tab) finishes in less than 10 min, the job needs to wait for the next "Run Details" status analysis to be considered as completed.

Therefore, use the "Run Details" timing to understand total system resource occupation and the Metrics tab timing for evaluating the replication performance.

SAP Help: Monitoring Flows

KBA , DS-DI-RF , Replication Flow Runtime , How To