Troubleshooting ControlUp Trigger Not Working

A user was having trouble with their trigger not working, and questions were raised about setting values and checking boxes. It was suggested to remove "from this state" as it was optional, and to try setting a filter of from: greater than 30 to: less than or equal to 30. It was also noted that in the upcoming release of 9.0, this feature of seeing free space for mapped drives and being able to alert on them would be available. Finally, it was suggested to remove "from this state" and check if the monitor had to be restarted.

Read the entire ‘Troubleshooting Trigger Not Working’ thread below:

greetings friends. Any idea why my trigger isnt working? (values are set high just to test) ik included " include disks that were just discovered"

Have you tested the trigger by removing everything "from this state" since it’s optional? I always leave it blank and my triggers fire off just fine since I always make sure to check the box at the bottom.

Maybe they go to 30.5 and are in the gap of your filter. Try from: greater than 30

To: less than or equal to 30

We have this feature coming in 9.0 to see the free space for all mapped drives for each user and be able to alert on them @member (It can’t come soon enough I’ve been pushing for this for a bit 💩)

I’d probably remove the From this State for now.

The pic of the 25% free space, was that already in that state when you created the trigger?

If that is the case, restarting the monitors would cause it to fire, I suspect.

Continue reading and comment on the thread ‘Troubleshooting ControlUp Trigger Not Working’.  Not a member? Join Here!