2026-06-25

Improvements

• The TimescaleDB Historian bridge template now creates all of its tables, types, and functions in a dedicated umh schema (for example umh.value_<contract> instead of value_<contract>), keeping the historian's objects separate from anything else in your Postgres database. New deployments use the umh schema automatically, and the database setup no longer needs a grant on the public schema. If you already deployed an earlier version that used the public schema, the bridge editor now includes a short one-time migration guide (a few ALTER ... SET SCHEMA umh statements) to move your existing tables into umh before redeploying, so your historical data is preserved.
• Deploying a bridge now saves your full configuration in one step. If the deployment does not reach a running state in time, your configuration is kept instead of being discarded and you are taken to the bridge's editing view, where you can adjust it and deploy again. Previously a failed first deployment could leave you without a saved bridge.

Fixes

• During sign-up, choosing a company name that was already taken showed "You are already onboarded" and redirected you to the home page, even though your account was never created. The onboarding form now shows "Please use a different company name" and keeps you on the page so you can pick another name and finish signing up.