I've recently turned on the integration and have found an issue where a ticket which is assigned to a staff member and where the ticket state was "assigned" was changed to "unassigned". I can't figure out how to affect this behavior. Just because the alert is still active is no reason to change the state unless the state was set to resolved. In this case it was not.
This looks fine..
As per ur earlier screenshot, it shows that the update happened at same time about alert being active and it got un-assigned...
-->Did the alert re-occur?
--> You might also have to check if there is any rule written on SNOW end which might be colliding with this.....just a guess...
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.