Seems that this is either a result of a corrupted database, or a combination of several bugs in Solarwinds?
If the record (of an object in Solarwinds) is stale and no longer exists, why was the alert triggered?
If the object does exist, and the alert was triggered correctly because of an issue with it, then Solarwinds' behavior must be a bug on two counts: (1) the alert points to a non-existent record, (2) does not offer any other way to track the issue (e.g. the node ID)
...and the database being corrupted is unlikely because SW runs integrity checks once a day, if memory serves me right?