Nightly build

October 26 Nightly

This release adds schema support to data flows, gives new screen elements a default data path, and fixes a Data Change Capture bug that affected scaled environments. 3 changes. Pre-release.

All nightly builds Subscribe

Pre-release. Nightly builds run in our nightly environment for testing and early feedback. Changes here can be revised or held back, and nothing on this page is a commitment for the next production release. For what is generally available, see production releases.
AI generated. These notes are written by AI from the build's changes, and AI sometimes gets things wrong. If you have questions, please contact us through Fuuz customer support.

Build: 2026-10-26 nightly
Date: Oct 26, 2026
Environment: Nightly
Changes: 3

Improved

You can now define an input schema (JSON Schema) on a data flow's Request node and an output schema on its Response node. The flow's inputSchema and outputSchema are available through the API, and payloads are checked against them. If a payload doesn't match the schema, the flow raises an error instead of running with bad data. Existing flows that have Request/Response nodes default to an open {} schema, so they keep working as before.
In the screen designer, new form inputs and table columns now get a default dataPath based on the element's System Name. Before, a screen would error at runtime if you dropped one of these elements in and didn't set a data path.

Fixed

Fixed a Data Change Capture bug in environments running more than one Data Change Capture instance. When a data model was deployed, only one instance picked up the new configuration. Because of this, change events for newly deployed models could be skipped and never recorded. Fields marked Sensitive could also be stored unredacted, and excluded-field, retention, and label-field settings were applied inconsistently. Every instance now reloads model configuration after each deployment.