Using Sessions in Streamline

Sessions are where you go to view what workflows are in progress within your Streamline project. This guide walks you through how to get started with sessions and track workflow progress easily.

Step 1: Give the Right People Access

Before starting a session, make sure everyone who needs to participate has access to the project.

• Navigate to the top right of the project page

• Click on “Access”

• Add any team members or collaborators who should be involved

Tip: Only users with access can view or interact with sessions.

Step 2: Start a New Session

Once access is set up, you’re ready to begin!

• Click the “New Session” button to initiate a new workflow

• A session will automatically begin from the first step of your configured workflow

Step 3: Track Sessions in Progress

After starting a session, you’ll see it listed in the Session Table. Here’s what you’ll find:

• Session ID – A unique identifier for each session

• Status – Shows whether a session is in progress, completed or failed

• Current Step - The current step of the session

• Step Started - The start date of the most current step in the workflow

• Error Description - Any known failures that have occurred during the session. Click Details to get more information on what happened. 

• Start date – Indicates when the session was initiated

If a session is still in progress, click the session link to open it. You’ll be taken directly to the most recent step, so you can easily resume progress.

Tip: Streamline automatically saves session progress — no need to start over if you step away!

Error Details

• Each errored session displays an error description explaining what went wrong and what can be done to resolve the issue

• Error details include the specific workflow step where the failure occurred

• Timestamp of when the error occurred is displayed

• Errors are categorized by type (e.g., validation, external service, authentication, configuration) so builders can quickly understand the class of problem

Note: Error details are scoped by existing project-level permissions. Users only see errors for sessions they already have access to view. Action buttons within error details (e.g., "Edit Dataset") are hidden for users who lack permission to perform that action. Notification preferences are configurable by builders with project edit access. For more information on configuring account notification preferences, please see this article. 

Reminder

Sessions help your team collaborate in real time or asynchronously. Make sure to keep your project access updated so the right people can pick up where others left off.