Here are some issues we are facing with TimeSeriesUploadQueue after migrating to lastest version :
- Unable to upload rows, though it says it has been uploaded in latest version
It says uploader uploaded x datapoints even though it doesnt (checked in ui and through api) , and uploaded rows is None even though there are datapoints to upload. Same code works fine in version 6.
![](https://uploads-eu-west-1.insided.com/cognite-en/attachment/f626a1d3-a038-4206-b76a-5903e3083801.png)
This is our post upload function:
![](https://uploads-eu-west-1.insided.com/cognite-en/attachment/73e82ac6-96a4-48b0-95c2-b1f7342f03c3.png)
- Wrong date range is uploaded in version 7. (happens on a random basis)
The target timeseries didnt exist before we run the extractor. The date range we were trying to upload in the first batch is October 25, 2022 11:38:38.553 PM - December 27, 2022 11:03:47.055 AM and in the second batch is December 27, 2022 7:03:47.055 PM to January 1, 2023 11:03:47.055 AM( all GMT times)
![](https://uploads-eu-west-1.insided.com/cognite-en/attachment/942ea712-7fe7-45b1-a0b2-e577e24efa68.png)
![](https://uploads-eu-west-1.insided.com/cognite-en/attachment/68b71afc-718b-4aa2-a99f-6c894529de81.png)
Both batch's upload failed according to sdk (error during callback, rows is NoneType), but somehow 50 datapoints in a completely different date range is written as observed through cognite ui and through sdk
![](https://uploads-eu-west-1.insided.com/cognite-en/attachment/fd9d401e-f8d7-4e00-a349-8238cd3c52f3.png)
- We also face below error every now and then on random basis, and other times it works fine on its own without any changes.
![](https://uploads-eu-west-1.insided.com/cognite-en/attachment/1d622465-0c9e-4740-a8c3-3b217c570074.png)