Following some station (data source side) power outages, a new bot use case cropped up in which the Tempest API data is not current. This in turn causes the "current" observations to return a blank/null dataset which is wasn't anticipated in the original design as it was unknown how the API would return as the "last known observation."
TL;DR: Add some basic and better/gentler error handling into the bot should alert or current observation data be blank/null.
Following some station (data source side) power outages, a new bot use case cropped up in which the Tempest API data is not current. This in turn causes the "current" observations to return a blank/null dataset which is wasn't anticipated in the original design as it was unknown how the API would return as the "last known observation."
TL;DR: Add some basic and better/gentler error handling into the bot should alert or current observation data be blank/null.