Prepare a useful support report

Record these details

• Application name and version; Workstation version if used; Hub build when relevant.
• Operating system/version, computer type and whether it is desktop or kiosk mode.
• Device models and connection types: USB, NDI, RTSP, SRT, RFID or another supported connection.
• OBS and plugin versions for production/review/camera problems.
• Exact error text, the time it happened and the time zone.
• The last successful action, the steps to reproduce and whether it happens every time.

Use this report format

Application and version:
Workstation / Hub version:
Operating system and computer:
Desktop or kiosk; screen size / displays:
Devices and connection type:
What I was doing:
Steps to reproduce:
Expected result:
Actual result and exact error:
When it happened (include time zone):
What works / what fails:
Changes since it last worked:

Collect diagnostics

Where available, use Workstation Help → Save diagnostics and the application's installation details. For native crashes, keep the OS crash report. Screenshots should include the relevant controls and message, not only an empty area. If a failure occurs during an update, preserve the install error before retrying.

Remove secrets

Do not include passwords, administrator PINs, stream keys, station pairing tokens, renewable license files, private room invitations or customer financial details. Mask those fields in screenshots. Do not send an entire private application data folder without reviewing its contents.

Preserve evidence without disrupting work

Record whether OBS or an output remained active after the app failed. End live work through its normal controls before maintenance. This guide prepares information; it does not submit a ticket or send a message automatically.