How to resolve discrepancy in the ‘log off session via script’ community script between User 1 and User 2 in ControlUp?

Two users noticed that a "Log off session via script" action was not working as expected, and discussed ways to troubleshoot the issue. They suggested that one user clear their ControlUp AppData directory or rename the ControlUp Store.xml file before relaunching to do this safely. The other user asked if there was an easier way to find out why the trigger was stopped working, and both suggested checking the event logs on the monitor for related event ID 5000/5005. Support ticket could also be launched if troubleshooting does not reveal the cause.

Read the entire ‘Troubleshooting Trigger-Based Action Issues in ControlUp 8.7’ thread below:

We encounter something strange. It seems that the community script part in the console for user 1 is not the same as for user 2. We noticed this after finding out a certain Trigger based action is not working ( logging off sessions after 4days. Any clue ? Version is 8.7. th script is called "log off session via script" . We use this Action for years.

Hey Nico

This script was renamed recently due to a naming conflict. Log off session via script is the correct name. Perhaps if the user in screen shot one clears their CU AppData they will get the correct results as well. DANGER, WILL ROBINSON: clearing that AppData will also clear some locally stored stuff like Draft scripts!

"Delete or rename the ControlUp directory in your personal “Application Data” folder. You can access this folder by clicking Start > Run and type %appdata%"

I think you can just renamed to .old this file and relaunch –

%appdata%\ControlUp\ControlUp Store\ControlUp Store.xml

@member I will ask Marcel to do so 🙂

"I think you can just renamed to .old this file and relaunch" –> yeah, if you want to do it safe and boring…

is there an easy way where we can find that the trigger is not working anymore? for others we can see it in the incident pane or in the eventlog but since we have quite a few monitors it is not really convenient checking all the logs ( and no we cannot do that from the realtime console since our network does not allow that )

Since the monitor is the main entity that carries out those triggers, we’ll need to know something via monitor logs OR event viewer. E.g. do you see any 5000/5005 event id’s in the monitor related to the trigger?

But ideally if you don’t find the reason, sounds like a support ticket and to be investigated. (not by me unfortunately 😞)

If the trigger has a follow-up action "record an event in the application log" it should be on the monitors (or to be exact, on the monitor that’s connected to the machine/agent the trigger should fire on/vs.

Continue reading and comment on the thread ‘How to resolve discrepancy in the ‘log off session via script’ community script between User 1 and User 2 in ControlUp?’.  Not a member? Join Here!