Handling Script Failures and Output in ControlUp Workflows: Error Ignoring, Conditional Logic, and Feature Updates

In a ControlUp workflow, users may want to handle script failures gracefully, akin to a “try-catch” mechanism seen in traditional programming. A user inquired about running an alternative action when a script run on a device fails. Currently, if the script fails, the workflow ends with an error, and no subsequent action is triggered automatically. The recommended approach is to use the “Ignore Error” option on the “Run Script” node, which prevents the workflow from stopping on error. Afterward, an “If Else” node can be added to check the status of the “Run Script” node and conditionally execute alternative actions based on success or failure. This method enables branching logic without halting the workflow.

A related challenge encountered was handling multiline output messages from scripts. The native ControlUp environment does not currently support converting multiline output into a single line with or without explicit newline characters such as “\n”. The ControlUp team acknowledged this need and plans to introduce this string transformation functionality soon, with expectations for release within a week. While this feature is pending, custom scripting or intermediate handling outside ControlUp might be required to process multiline outputs.

Users also raised the idea of more advanced scripting capabilities within workflows, such as embedding secure, sandboxed JavaScript actions or subflows callable like functions. The team confirmed interest in this concept but noted that it is not currently on the immediate roadmap and will require future prioritization.

Finally, a limitation was noted: timeout errors from script execution (defaulting to 60 minutes) cannot be ignored by the “Ignore Error” setting; when a script times out, the workflow fails by design. The ControlUp team is investigating possible improvements to how timeouts are handled in workflows.

For now, users can implement error handling in workflows using the “Ignore Error” flag combined with conditional checks but should be aware of limitations around timeout errors and multiline output processing. Updates and added features are in development to enhance workflow flexibility and scripting capabilities. For more details on creating and managing workflows, users can visit the official ControlUp documentation at https://docs.controlup.com or the ControlUp Academy at https://cuacademy.controlup.com.

Read the entire ‘Handling Script Failures and Output in ControlUp Workflows: Error Ignoring, Conditional Logic, and Feature Updates’ thread below:

Is it possible to do a sort of ‘try catch’ within a flow? For example; I have created a workflow which will run a script on a device. Sometimes this script failed for some reason. When failing, I want to run another action.

Now the workflow ends with a failed error, without any change to run action when failed.

Hi Rico.
You can use “Ignore Error” in the “Run Script” node

after “Run Script” just add the “If Else” node and check there the status of “Run Script”

Hey, that is awesome! Works like a charm. Now I have the following challenge; the output message is not single line. It contains linebreaks. Is there anyway to convert this to single line?

—, Nope. We will add something like this for you.
Am I correct that you need something to convert
“`Aaa bbb
ccc ddd“`
to
“`Aaa bbb ccc ddd“`?

Yes, or even better: \n

What about custom javascript code/scripting? Must be very secure ofc, and sandboxed. For example create a flow with javascript action. Call it from another flow as sub flow. Kind of functions 🙂

after running a script, the action failed if the script is timed out (60min default). The ignore on error option is ignored and the flow will be failed. By design?

—,
Timeout errors are can not be ignored for now. We need to think what we can do here. I will be back to you with answer soon.

Regarding scripting node – yep, I would like to do it. But this is not on our road map for this or next month for now. But due to mentions about it in community, I will try to push it up.

Regarding transforming multiple line string into one line string – we will add this ability very soon. I think next week on Wed you will be able to use it.

Continue reading and comment on the thread ‘Handling Script Failures and Output in ControlUp Workflows: Error Ignoring, Conditional Logic, and Feature Updates’.  Not a member? Join Here!