Back to Bentley
Llamaha icon

Bentley Application

OpenFlows Hydraulic Toolset

Use this guide when OpenFlows Hydraulic Toolset will not sign in, cannot open the model, module, or project folder you expect, or behaves differently after a computer, version, or workspace change.

Reviewed April 2026

Application Guide

Overview

OpenFlows Hydraulic Toolset is part of the Bentley application family used for design, review, modeling, or project work.

Most OpenFlows Hydraulic Toolset issues come from Bentley sign-in, CONNECTION Client state, product-version mismatch, missing workspace standards, or project data that is not reachable from the computer.

Plain English

What this app is usually used for

Hydraulic modeling bundle that may include multiple related OpenFlows capabilities.

It is part of the Bentley family covered in our app help.

Common problems

Common problems

Bentley sign-in or entitlement does not look right

OpenFlows Hydraulic Toolset opens, but the expected account, entitlement, or product access is missing.

Likely fix

Sign out and back in with the correct Bentley account, then compare the product entitlement and message before reinstalling.

What to collect

Send the Bentley account shown, the exact message, and whether other Bentley apps sign in correctly.

Project, data source, or workspace content is missing

OpenFlows Hydraulic Toolset launches, but the expected model, module, or project folder is missing or does not load correctly.

Likely fix

Confirm the project path, data source, and workspace standard against another approved computer before changing local files.

What to collect

Send the model, module, or project folder name, the path or data source shown, and a screenshot of what is missing.

First things to try

First things to try

Quick checks before you change anything

  • Can you sign in with the Bentley account your company expects?
  • Is the problem opening OpenFlows Hydraulic Toolset, opening one model, module, or project folder, or seeing the correct tools and standards?
  • Did the issue start after a new computer, update, password change, or project move?
  • Can another approved computer open the same project or data source?

Try these fixes first

  • Compare the affected project or file with a second known-good one before reinstalling the app.
  • Keep the exact Bentley account, app version, project name, data source, and workspace name ready for support.
  • If workspaces, standards, fonts, or templates are missing, compare with another approved computer before clearing local data.

Slow down

Do not do this yet / warnings

Avoid these until support says it is safe

  • Do not clear ProjectWise saved local data or local work areas until checked-out file ownership is confirmed.
  • Preserve project models and shared settings before uninstalling the bundle.

What support needs

What details support needs

Send these details

  • A screenshot of the exact OpenFlows Hydraulic Toolset message or missing screen.
  • The Bentley account shown in the app or CONNECTION Client.
  • The OpenFlows Hydraulic Toolset version shown in the app.
  • The affected model, module, or project folder name and where it should be available.
  • Whether another approved computer can open the same item.

Licensing & access

Licensing / access notes

Licensing / access checks

  • OpenFlows Hydraulic Toolset usually depends on the correct Bentley account, product entitlement, and any project or data source permissions your company assigns.
  • If the app opens but says trial, unlicensed, or shows missing products, capture the account shown and the exact message before reinstalling.
  • If the project or data source is missing after sign-in, the access path or workspace may matter more than the local install.

More checks

More setup checks

Install / update basics

  • Use the company-approved OpenFlows Hydraulic Toolset version for your project team.
  • Restart the computer after install or update if Windows or the installer asks you to.
  • Open CONNECTION Client or the Bentley sign-in prompt and confirm the expected work account is active.
  • Test one known-good project, data source, or file before opening the exact item that failed earlier.