Properties and classification set incorrectly in significant burst alerts
The kafka notices associated with S230808i, the first significant alert of O4 that only had a cWB g-event, were sent out with a bunch of links to non-public files in the superevent. These links were in the event.properties and event.classification sections of the notice, which should be empty for burst events. One example of a messed up notice can be seen here.
Update 1: It appears this only happened in the initial alert, not the preliminary alerts.
Update 2: This alert did not get sent via SCiMMA, because it didn't pass the runtime validation check used in the avro serialized messages. That resulted in this sentry error.
Edited by Cody Messick