There is some wonky behavior with regard to active alerts from the NWS API. When using the default values from config/nws.php.example ('Immediate,Expected,Future,Unknown') cancelled alerts may still show up until the original alert expiration date has passed. Dropping the Future alert option solves this problem but fails to then identify non-severe (e.g. 'watch') alerts.
Dropping the urgency parameter from the API call seems to address this issue entirely; more testing is necessary to verify. If so, dropping or modifying how the urgency parameter is handled (e.g. allow the bot host control over whether or not to use it) would be a reasonable idea.
There is some wonky behavior with regard to active alerts from the NWS API. When using the default values from
config/nws.php.example('Immediate,Expected,Future,Unknown') cancelled alerts may still show up until the original alert expiration date has passed. Dropping theFuturealert option solves this problem but fails to then identify non-severe (e.g. 'watch') alerts.Dropping the
urgencyparameter from the API call seems to address this issue entirely; more testing is necessary to verify. If so, dropping or modifying how theurgencyparameter is handled (e.g. allow the bot host control over whether or not to use it) would be a reasonable idea.