Steps to reproduce:
1. Open a pipeline that was deployed roughly a week ago and has couple of runs.
2. Choose a run and try to get metrics(say 'user.<stage-name>.records.in' for any stage in the pipeline for that particular run.
3. In the POST metrics api call (/v3/metrics/query) set "aggregate: false" in the "timeRange" object in "body".
A time series data for the number of records that went in to the stage for that particular run
An empty series with no data point.
What makes this misleading is when the same metrics call is made with "aggregate: true" we get a single data time series with "time: 0" and "value: NN". which is correct.
The pipeline that I tried is omintureHitsPipeline and tried querying data for `BrowserData` source node.