Skip to content

Debug Print

A debugging utility node that logs an input value and its type/structure to the console, then passes the value through unchanged. It provides concise representations for complex data (e.g., tensors show shape, containers are summarized).
Preview

Usage

Use this node anywhere in a workflow to inspect intermediate data without altering it. Insert SaltDebugPrint between nodes, give it a clear label, and check the console/log output to verify values, shapes, and structures during troubleshooting or development.

Inputs

FieldRequiredTypeDescriptionExample
valueTrueWILDCARDAny value to be inspected and logged. Supports scalars, strings, dicts, lists, tuples, tensors, and other objects.['cat', 'dog', 'bird']
labelTrueSTRINGA short label to identify this debug print in the logs.embedding_check

Outputs

FieldTypeDescriptionExample
valueWILDCARDThe original input value, passed through unchanged for continued processing.['cat', 'dog', 'bird']

Important Notes

  • The node logs at debug level; ensure your logging configuration shows debug messages to see output.
  • Tensors are summarized as Tensor[shape] rather than printing full contents.
  • Lists, tuples, and dicts are printed recursively in a compact representation; very large structures may still produce lengthy logs.
  • Even if logging fails, the node returns the original value unchanged.
  • The label input is required and is included in log messages to help identify the source.

Troubleshooting

  • No output appears in console/logs: Ensure debug-level logging is enabled and the runtime log view is open.
  • Output is too verbose: Place the node only where needed or reduce the size of structures being logged.
  • Need full tensor values: Convert tensors to smaller summaries (e.g., stats) upstream before passing into this node, since it prints only shapes.
  • Label missing or unclear: Provide a unique, descriptive label to distinguish multiple debug prints in the same workflow.