Troubleshooting and limits
Find the next useful step when something does not work as expected.
I cannot find my work
Check the account, project, and chat you have open. Use Quick Search before creating a replacement.
If a generation or save was interrupted, reopen the conversation and read its last status.
A generation failed or stopped
Read the error in the conversation. It may point to a usage limit, connection problem, missing dependency, or unsupported input.
Keep the prompt and references. Resolve the cause before retrying, and avoid submitting multiple requests while a generation is still running.
The wrong part changed
Check the selected component or element. Clear stale references and snips, then say what should change and what must stay.
For repeated elements, include distinguishing content or target a larger region. Return to a working version if the result went off course.
The preview differs from my app
Make sure the destination includes the expected dependencies, fonts, and assets. Global styles and application context can change appearance and behavior.
Tenor previews frontend work. Real authentication, backend data, permissions, and deployment belong in the destination application.
A connection or feature is unavailable
Check the relevant connection in Settings and follow its reconnect instructions. For generation access and usage, open Settings → Billing.
A failed connection or exhausted allowance is different from an unsuccessful design request. Resolve the availability problem before changing your prompt.
Handle source material carefully
Only use code, images, and files you have permission to bring into Tenor. Keep credentials and unnecessary personal data out of prompts and references.
Review content and permissions before sharing a preview or enabling agent access. The Privacy policy explains Tenor’s data practices.