How to View the Output of a Notebook Process

Syntasa allows you to productionize data science workflows by embedding Jupyter Notebooks directly into applications as Notebook Processes. After a job containing a Notebook Process is executed, you can inspect the full execution output—including rendered cells, tables, charts, and execution metadata—directly within the Syntasa user interface.

This article explains how notebook outputs are generated, where they are stored, and how to view and troubleshoot them.

Overview

When a Notebook Process runs as part of a job:

  • The system executes the notebook using a dedicated Notebook Executor.

  • A timestamped output notebook (.ipynb) is generated for that execution.

  • The output file is stored in the workspace execution directory.

  • The Syntasa UI retrieves this file and renders it as a high-fidelity preview.

This approach ensures that what you see in the UI accurately reflects the notebook’s final state at execution time.

Steps to View Notebook Output

1. Navigate to the Application Workflow

Open the application that contains your Notebook Process.
Confirm that you are viewing the same environment (Development or Production) in which the job was executed.

2. Locate the Notebook Nodes

On the workflow canvas, a Notebook Process is represented by two related nodes:

  • Notebook Process Node
    Defines the source notebook, runtime, and execution settings.

  • Output Node
    Represents the concrete results generated by a specific execution of the notebook. There's is always one default output which is different than the other output. Default output only shows the logs and notebook cell level execution result. Other output is the regular output those store the data been written through notebook

3. Open the Output Configuration Panel

Click the Output node (typically labeled Output or a custom name).
This opens the configuration panel on the right side of the screen.

4. Review Execution Metadata (Details Tab)

The Details tab provides execution-level metadata, including:

  • Username – The user who triggered the job execution

  • Execution Time – When the notebook was processed

  • Notebook Name – The source notebook used

  • Environment – The environment (for example, dev or prod) where the job ran

This information is useful for auditing, troubleshooting, and validating execution context.

5. View the Rendered Notebook (Output Tab)

Switch to the Output tab to view the notebook results.

  • Rendered Content
    The notebook is displayed exactly as it appeared after execution, including:

    • Cell outputs

    • Printed dataframes

    • Visualizations (such as Matplotlib or Plotly charts)

  • Markdown Rendering
    All markdown cells are fully rendered, preserving documentation and narrative context.

  • Latest Execution by Default
    The UI automatically uses the most recent Execution ID to fetch and display the latest successful output.

Technical Details

Output Storage Path

Notebook execution results are stored in cloud storage using the following structure:

syn-workspace/workspace_executions/[workspace_key]/users/[owner]/notebooks/[notebook_key]/[execution_id]/[notebook_name]-output.ipynb

Executor Logic

  • The Notebook Executor captures the remote output path from execution logs.

  • A preview event is triggered to notify the platform that a rendered notebook is available.

  • The UI retrieves the generated .ipynb file and renders it in the Output tab.

Preview Behavior

  • The UI fetches the entire generated .ipynb file for rendering.

  • What you see is a faithful representation of the executed notebook, not a partial or summarized view.

Troubleshooting

“No preview available for this notebook”

This message may appear for one of the following reasons:

  • Job Failure
    If execution failed before an output file was generated, no preview will be available.
    → Check the job Status tab or execution logs for errors.

  • Permissions Issue
    Your user may not have access to the cloud storage bucket where execution results are stored.

  • Missing Output Node
    Ensure the Notebook Process is correctly configured with an Output object on the canvas.

Preview Is Outdated

The Output tab always displays results from the latest successful execution.

If you recently modified notebook code but did not re-run the job:

  • The preview will continue to show results from the previous run.

  • Trigger a new job execution to refresh the output.

Summary

Viewing Notebook Process output in Syntasa provides a seamless way to validate, analyze, and share results without leaving the platform. By rendering the executed notebook directly in the UI—with full support for charts, markdown, and metadata—Syntasa ensures transparency, traceability, and confidence as notebooks move from experimentation into production workflows.