Alerts API
#504
Replies: 1 comment
-
There is an issue where alerts that have been updated sometimes remain on the active endpoint too long. This will be fixed in a software update. A possible workaround until then is to cross-check the expiredReferences of all alerts in the endpoint. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I notice fairly regularly that a VTEC event will get "stuck" in the alerts API and remain there until the original expiration time, even though it has been updated via CON, UPG, etc.
For example on https://api.weather.gov/alerts/active/area/IA as of 11:30 on the 31st:
The timestamp associated with that VTEC is 304 AM CST Thu Dec 30 2021. It has been updated three times since that point (over 24 hours later), including an upgrade:
519 PM CST Thu Dec 30 2021 /O.CON.KDVN.WS.A.0005.220101T1200Z-220102T0600Z/
902 PM CST Thu Dec 30 2021 /O.CON.KDVN.WS.A.0005.220101T1200Z-220102T0600Z/
325 AM CST Fri Dec 31 2021
/O.UPG.KDVN.WS.A.0005.220101T1200Z-220102T0600Z/
/O.NEW.KDVN.WS.W.0006.220101T1200Z-220102T0600Z/
And yet it still sits there.
This isn't a one-off occurrence either, it happens semi-regularly.
Beta Was this translation helpful? Give feedback.
All reactions