Help with orphaned trigger
Greetings!
So I have a host which has now been deleted, which I'm still receiving trigger alerts for. Wondering if I can get some assistance in finding/purging whatever database data is causing this!
Brief overview:
-Host was on 1.8.x, connects to a local 1.8.x proxy at the site.
-Host had this particular test (smtp_perf) applied to it via a template
-I removed the template off the host, but still received the trigger alerts
-I then deleted the host altogether but I'm still receiving the trigger alerts.
Proxy and server have since been upgraded to 2.0.2, as I wanted to upgrade anyway and was hopeful this might clean up the error. It didn't, but I'm still happier on the new version!
thanks for any pointers!
Brett
So I have a host which has now been deleted, which I'm still receiving trigger alerts for. Wondering if I can get some assistance in finding/purging whatever database data is causing this!
Brief overview:
-Host was on 1.8.x, connects to a local 1.8.x proxy at the site.
-Host had this particular test (smtp_perf) applied to it via a template
-I removed the template off the host, but still received the trigger alerts
-I then deleted the host altogether but I'm still receiving the trigger alerts.
Proxy and server have since been upgraded to 2.0.2, as I wanted to upgrade anyway and was hopeful this might clean up the error. It didn't, but I'm still happier on the new version!
thanks for any pointers!
Brett