Session Management in Model Pipeline

Overview

The application now supports enhanced session management for executing model pipelines. This feature resolves earlier limitations where pipeline executions were bound to an implicit session, with no visibility or control for users. The update brings consistency between pipeline and notebook behavior. Each session has its own context, keeping pipeline and notebook outputs in sync.

Figure 11-111 Model Pipeline Session screen

Figure 11-112 Session drop-down screen with multiple sessions shared between Pipeline Canvas and Notebook

Key Features

• Session dropdown available in both pipeline and notebook tabs.
• Default state is No session selected' users must create or choose a session.
• A prompt appears if execution starts without a selected session.
• Sessions can be created, switched, reinitialized, or cleared.
• Selected session syncs automatically across notebook and pipeline.
• Pipeline outputs and notebook results are isolated per session.

Note:

• Session selection is mandatory before running pipelines.
• Sessions help isolate workflows, making debugging and reruns easier.