When a Script-Based Action (SBA) is created in the ControlUp Real-Time Console, it typically becomes available in the ControlUp web app almost immediately. The synchronization between the console and the web app occurs through the ControlUp store configuration, which is propagated via the monitor cluster. Generally, no additional manual steps are necessary for the new script action to appear in the web app interface.
However, in scenarios where the script action does not immediately show up in the web app, several troubleshooting steps can help resolve the issue. The first recommended approach is to simply refresh the web console page to ensure the interface updates with the latest configuration changes. If the script action still does not appear, verifying user permissions is crucial, as lack of appropriate access often causes visibility problems. An explicit save of the configuration from the console using the File -> Save Configuration option may also accelerate the propagation process. As a last resort, restarting the monitor cluster can force synchronization across components.
The most common root cause for delays or failures in SBA availability in the web app is permission settings. Ensuring users have the necessary rights to access and execute the script actions is essential. This sequence of steps—refresh, check permissions, save config, restart the cluster—provides a structured approach to troubleshooting SBA visibility issues across ControlUp environments.
For further details on managing Script-Based Actions and permission configurations, refer to the official ControlUp documentation at https://docs.controlup.com and explore ControlUp Academy resources at https://cuacademy.controlup.com.
Read the entire ‘Troubleshooting Script-Based Action Visibility Delays Between ControlUp Console and Web App’ thread below:
When you create a script action in the real time console, how long should it take before that action is available in the web app or is there something I need to do in the web app to make it available.
Should not take long, but I would use the File -> Save Configuration option at the Console if you want to speed up the process
Hi Greg, to add to what Abel said, you should not have to do anything. When you create an SBA in the console, it is written to the Controlup store configuration and pushed out to the web app through your monitor cluster.
If the SBA does not show up, you have the following options, in order of preference:
• refresh the web console
• Check permissions
• Save config, as Abel pointed out
• Restart the monitor cluster.
most of the times its permissions from what I have seen
Continue reading and comment on the thread ‘Troubleshooting Script-Based Action Visibility Delays Between ControlUp Console and Web App’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI, ControlUp Scripts & Triggers