Data taking a long time to update.

[chasbearden]

I have gone throughout the entire Ignition Perspective application I am building to make sure I only have items that are calling for API information in two different groups, one group that calls hourly and updates the daily forecast information and one group that calls for data every 5 minutes for the hourly forecast information. Save for two hourly scripts that are currently set to every 30 seconds for testing purposes, everything else fits within those two groups. I have been keeping a time on the "startTime" readout I have on my hourly forecast readouts and they are taking anywhere from a few minutes to nearly a whole hour to update to the latest information/time. The overall goal is to be able to read out weather data for 9 different locations that the displayed location will be selected by the user.

I am running timed gateway scripts that write information to tags and then different labels look at the information on those tags.

Currently I am unsure if the data I'm calling is returning stale/outdated, or if it is another issue. Recently I noticed that sometimes when I refresh the API information when looking at it in my web browser it is also taking a long period of time to update. This second issue when looking at information in my web browser seems to be hit and miss though.

[sullynole]

startTime should only change once an hour for the first period on the hourly endpoint so that makes sense. updateTime will show the last update to any of the forecast grids. The WFO is only required to update every 12 hours and the periods move forward in time each hour, so those are the longest periods you might expect to wait for a change. They can be more often, but sub hourly updates are not common that I am aware.

[dwhitemv25]

Make sure you're monitoring the cache headers returned from the API call. There is a caching layer between you and API and the max-age on things like hourly forecasts are an hour (3600 seconds). Hitting it any faster frequency than the max-age (for the same location) is returning the same data over and over. Hourly won't "tick over" until the cache updates from the origin.