Skip to content

Output Panel

The Output Panel displays results from script execution, with different views depending on the selected mode.

The Output Panel sits below the code editor and includes:

  • Tab selector for different output views
  • Execution status badge showing run state
  • Duration timer for execution time
  • Controls for copy, fullscreen, and clear

Drag the divider between the editor and output panel to resize.

Output panel showing raw script output

The complete text output from your script execution:

  • Full stdout from the collector
  • Includes warnings, errors, and debug messages
  • Preserves formatting and line breaks
  • Displayed in monospace font
Raw output tab

The status badge in the header shows the current state:

StatusDescription
Running Script is executing (with spinner)
Complete Finished successfully
Error Script failed with an error
Timeout Exceeded time limit
Cancelled Execution was cancelled by user

The execution duration displays next to the status badge (e.g., “2.34s”).


IssueSeverityDescription
Empty instance IDErrorInstance ID is required
ID exceeds 1024 charsErrorMaximum length exceeded
Invalid ID charactersErrorContains spaces, =, :, \, or #
Name exceeds 255 charsWarningMay be truncated
Duplicate instance IDWarningSame ID appears multiple times

When a script fails, the Raw Output tab shows:

Error messages appear in red text with stack traces and diagnostic information. Partial output may appear if the script produced output before failing.


ControlAction
CopyCopy the entire raw output to your clipboard. Captures all content even if truncated in display.
FullscreenExpand the panel to fill the workspace. Press Esc or click ✕ to exit.
ClearReset the panel to empty state. Also clears automatically when starting a new execution.

  1. Use println statements liberally during development
  2. Print variable values and intermediate results
  3. Once logic is verified, format output for the target mode
  1. Check the Validation tab after each run
  2. Fix all errors before deploying to production
  3. Address warnings when possible—they indicate potential issues
  • Use fullscreen mode for better readability
  • The copy button captures all content, even if display is truncated
  • Add summary lines at the end of your script for quick verification