# Better\_forecast JSON issues today?

**URL:** <https://community.tempest.earth/t/better-forecast-json-issues-today/27273>\
**Category:** Developers\
**Tags:** tempest\
**Created:** [May 22, 2025, 9:47pm UTC](https://community.tempest.earth/t/better-forecast-json-issues-today/27273 "2025-05-22T21:47:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![alostengineer](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/alostengineer/32/17340_2.png) [@alostengineer](https://community.tempest.earth/u/alostengineer)\
**Post date:** [May 22, 2025, 9:47pm UTC](https://community.tempest.earth/t/better-forecast-json-issues-today/27273/1 "2025-05-22T21:47:20Z")

</div>

Hi all!  
I am developing a Rust app that’s basically a weather dashboard (mostly to learn to use generative AI in coding) and today I noticed a lot of issues when pulling from the `better_forecast` endpoint. Most commonly, the timestamp would be missing from the head of the JSON payload but often other values (UV popped up more than a few times as missing) would be missing, and my json parser, expecting those values, would puke and abort, leading to a lack of data to display on the dashboard. As far as I could tell, this was on the API side; both my functional production code and my dev code was exhibiting the same behavior with the same missing values, and when I went to the endpoint myself and grabbed the JSON, those values were indeed missing despite being documented as non-optional fields in the API documentation. Any clarity is appreciated! (In any case, it prompted me to implement forecast caching so that I can absorb short outages so net positive result. `https://gitlab.com/alostengineer/tempest-wx-interface/` for anyone interested.)  
Thanks!