@MakerOfCARROT I'm having an issue with AQI as a complication on my watch (I like having it in conjunction with the precip chance, so I'd prefer not to use a dedicated and inferior app for that data)
I guess because AQI can't be predicted/forecast, there's no data to cache when the watch pulls data. I'm finding very very often that I see N/A for AQI, as if it takes too long to get that data and just gives up. I know a long time ago, when time travel was a feature you cached data for the forecasts and IIRC this was used as a fall back when updates weren't possible. I assume you do the same now.
This has been an issue for a while, but I didn't mention it because opening the app would also show N/A for AQI readings so I assumed unavailability for whatever reason. However, recently I've been able to see a value for AQI immediately in the watch app upon touching the complication showing N/A. The data is either there and not being passed to the complication (due to time constraints?) or you've already built in some kind of redundancy that hasn't made its way to the complication/watch faces.
I was wondering if you might be able to cache the existing reading for the next hour or two in order to prevent this kind of thing?