Report a bug
Find a bug. Keep Studio for life.
While the app is in open testing, one usable report earns a Studio lifetime key. This page says what counts, how to send it, and what happens after.
Write a report See known issues first
Open-test reward
1 usable report
Studio lifetime key
Three PCs · every 1.x release · $449 value
Issued when your report is confirmed, not when the bug is fixed.
A reply within 2 working daysFrom the person who builds the app, not a bot.
A ticket number at onceEvery report gets one, so you can follow it on the known issues page.
Credit in the release historyBy name or anonymously, your choice.
What counts as a usable report
Usable means someone else can make the problem happen again, or see exactly where it happened.
Counts
A bug you can make happen again, with the steps
A crash, with the log the app attaches
A service behaving differently from its own documentation: a wrong length, a 401, a wrong price
A missing step that stops a real episode from being finished
Wrong, clipped or untranslated text in any of the twelve languages
Does not count
“It does not work”, with no steps and no log
The AI model’s own taste, like a face it drew oddly. That is the service, not the app
A known issue repeated without anything new
Asking for what the app says it will not do, like a macOS build or timeline editing
From the app
Best
Help → Report a problem. It attaches the log, a screenshot, system info and the jobs involved. API keys are stripped out.
With the form below
For when the app will not install or open, or you are on another PC.
In the group
For a quick question first. A bug raised there is turned into a ticket for you.
DIAGNOSTIC TRIAGE CONSOLE · DIRECT ENGINEERING QUEUE
The report form
Filled in with an example of a good report. Replace it with yours, or click Clear example to start fresh.
This is a
How bad is itSelect production impact level
Attachments
Drop the log, screenshots or a short screen recordingUp to 50 MB · Sent from the app,
scena-1.1.0.log is attached automatically with API keys scrubbed.
Browse files…
scena-1.1.0.logSample log24 KB
queue-veo-waiting.png380 KB
Credit in the release history
The draft stays in this browser. To send the report and attachments, open Report a problem in Scena Studio.
This browser could not save the draft.
Zero API keys transmitted
≤ 48h core engineer triage
Permanent Studio key ($449)
Is it usable?
5/5 · 100% READY
A title that names the problem
Steps someone else can follow
What you expected instead
The build and the screen
The log attached
Usable: Qualifies for a permanent Studio key ($449 value)
A title that helpsTRIAGE EXAMPLE
Too vague · Delayed triage×
“Veo broken”
Actionable · Instant reproduction✓
“Veo jobs stay ‘waiting’ after the key is renewed”
What is never sent
API keys, prompts outside the jobs you attach, and your rendered media never leave your PC. Logs are scrubbed client-side before upload:
[14:22:08] job=SC04 svc=veo_3_1 state=WAITING_KEY
[14:22:08] api_key=[REDACTED_LOCAL_DPAPI]
[14:22:09] media_dir=[STRIPPED_USER_PATH]
Open-Beta Bug Bounty Guarantee
1. Ticket ID:Assigned immediately and tracked publicly on Known Issues.
2. Key ($449):Issued the same day our engineers reproduce the issue.
3. Lifetime:Unlocks all Studio features for every
1.x release.
After sending from the app
1
Received
At once
A ticket number, and a copy by email.
2
Confirmed usable
Within 2 working days
Reproduced, or one question asked if something is missing.
3
Key issued
Same day
The Studio lifetime key goes to the email on the report.
4
Listed
Same day
On the known issues page, with a workaround if there is one.
5
Fixed and credited
Next patch or minor build
Named in the release history, if you chose credit.
Rules of the open test
One Studio lifetime key per person, however many reports you send.
A report on a known issue counts when it adds what was missing: a log, steps that reproduce it, or another service it happens on.
If two people report the same new bug, each report that is usable on its own counts.
Reports come from real use. The attached log shows the jobs that ran.
The offer ends when the signed build ships. Reports sent before then are honoured after it.