Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:3
-
Sprint:TSSW Sprint - Jan 30 - Feb 13
-
Team:Telescope and Site
-
Urgent?:No
Description
For some yet undetermined reason, the API call returns a 400 bad request response on occasion.
It seems like the MeteoBlue API will sometimes return less than the expected 382 values. It will return 370 for hourly trends which then causes the DDS write to fail. The 400 bad requests may be related to the API configurable limit but not fully verified. I added a padding function to fill up the data and am now validating that it mitigates the issue. Also sending an email to MeteoBlue to see why the API returns truncated values.