< Back to all releases
Management Console

2026-06-30

Improvements

  • Enterprise companies that sign in through their own SSO connection can now invite UMH value engineers to help manage their instances. Previously, an invitation sent to a @umh.app address was tied to the company's own connection, where the engineer has no account, so the invitation could not be accepted. Now, invitations to @umh.app addresses use UMH's Google Workspace login, which is enabled on your organization automatically, so your UMH value engineers can accept the invite.

Fixes

  • Classic instances showed Docker stop, pull, and run commands in the update instructions dialog — instructions that don't apply because Classic runs on Kubernetes, not as a standalone Docker container. The dialog now explains the correct upgrade path and links directly to the instance details page. UMH Core update instructions (Docker Run and Docker Compose) are unchanged.
Update dialog for a Classic instance showing the correct upgrade guidance and

Update dialog for a UMH Core instance showing the Docker Run and Docker Compose tabs

  • Naming a standalone flow the same as one that already exists on the instance is now caught as you type. The name field is highlighted and Save & Deploy is blocked. Previously the deploy appeared to start and then failed on the instance, because two flows with the same name resolve to the same identity.
Standalone flow form with a duplicate name: the name field is highlighted in red with the message
  • After deploying a standalone flow, the "Continue Editing" button now opens the flow's editing view as intended. Previously it only closed the dialog and left you on the create page.
  • For users testing the Write flows preview, add selection between time-series and relational data processing for read and write flows.
Discuss on Discord