> ## Documentation Index
> Fetch the complete documentation index at: https://help.ondeckapps.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Beta features in Relay

> Understand the actual beta-only tools, modules, and workflows currently exposed in Relay builds.

Relay exposes a few beta-only or beta-sensitive surfaces that should be tested carefully before you rely on them in a mission-critical workflow.

## Release features vs beta features

Relay `1.1.1` includes shipped features like the new home screen, startup file pinning, auto-save improvements, per-tab canvas sizing, and DiGiCo workflow upgrades.

Those are part of the main release track.

Beta features stay separate. In the current `1.1.1` cycle, the biggest example is the **YouTube Live Stream Monitor**, which should still be treated as test-only until it moves into the main release set.

## Where beta shows up

* the `Beta` page in `Relay > Settings`
* beta-badged modules in the module catalog
* beta-only device or model support
* beta-gated automation graph features
* beta or debug-only wireless diagnostics controls

## Current beta-sensitive areas

* NDI Feed remains a beta-sensitive module and should be validated on the real production network
* YouTube Live Stream Monitor is currently beta-only and should be tested with your real account, stream state, and dashboard persistence flow
* Shure and Live Transcription modules carry beta sensitivity in current builds
* Sennheiser module availability is limited to beta or debug builds
* beta-only Shure models include `ANX4`, `ADTD`, and `ADTQ`
* graph features like `If / Else`, `Variable`, and the `Vista` destination are beta-gated
* text-module behavior and graph runtime behavior deserve extra validation in real-world testing

## Beta tools in Settings

The Beta settings page currently includes:

* wireless diagnostics upload to Sentry
* beta feedback submission
* verbose wireless logging toggles for Shure and Sennheiser families
* beta update visibility

## Best practices

* isolate one beta variable at a time
* test with the real device or service involved
* validate behavior in both Canvas View and Live Mode
* keep a fallback plan before using beta workflows live

## Reporting beta issues

When a beta feature behaves incorrectly, document the expected behavior, the actual behavior, reproducible steps, and any available logs or screenshots, then send the report to `support@ondeckapps.com`.