Add a Result column to Tasks for raw script or task output

What:
Add a Result column to the Tasks view that surfaces the most relevant output from a task, especially for Scripted Actions.

Value:
This would dramatically reduce the effort required to validate outcomes, troubleshoot failures, compare results across many machines, and analyze consistency of script behavior.

Why this is needed:
Today, getting meaningful output from a task often requires opening the task details, scrolling through a large amount of infrastructure and orchestration noise, expanding logs, waiting for additional detail, and manually interpreting JSON or other low-readability output.

In many cases, the most important thing an admin wants is simply the actual output of the script or executable that ran.

Suggested behavior:
The Result column could either:

  • display a trimmed inline summary of the result, or
  • show a clickable icon that opens a modal with the raw output in a readable console-style format

That output should prioritize the actual task result over surrounding operational noise such as:

  • VM lookup steps
  • extension installation details
  • preparation steps
  • cleanup steps
  • extension removal details

Example:
If I run a Scripted Action against many session hosts, I want to quickly see which machines returned which outputs, without opening each task individually.

Why this matters in practice:
This would make it much easier to:

  • spot recurring errors across many hosts
  • group similar outcomes together
  • validate script reliability over time
  • improve scripts based on larger output samples
  • export meaningful results for analysis

For example, if 17 hosts return one specific string and 5 hosts return another, that pattern becomes useful immediately for troubleshooting and iterative script improvement.

Suggested enhancements:

  • Allow filtering by Result text
  • Allow export of Result in CSV/JSON
  • Preserve the raw output exactly as generated by the script or process

Related request:
This would pair very well with an aggregated Scripted Action runtime view by Workspace or Host Pool.

0

Comments (0 comments)

Please sign in to leave a comment.