0.15 Troubleshooting Without a Logs Page
Use visible workflow status, Credit Usage, deployment banners, and retry prompts when there is no general Logs page.
Quick Guide
Status: The current user product does not expose one general "Logs" page.
Use instead: Credit Usage, deployment banners, page-level errors, and the visible retry or review prompts on the current workflow.
Where to troubleshoot now
- Use
Credit Usagefor credit and AI usage history. - Use visible translation retry or review prompts when a translation needs follow-up.
- Use page banners and dialogs for the current action that failed.
What to capture before asking for help
- The exact page name.
- The exact banner or dialog text.
- The project name and time of the problem.
FAQ
Common questions for this workflow, based on the current SurtitleLive system.
Where should I look if there is no general Logs page?+
Use the visible page banner, retry or review prompt, Credit Usage page, or deployment status surface that belongs to the workflow you are troubleshooting.
How do I investigate AI or processing issues?+
Use Credit Usage for credit and AI usage history, then use the retry or review prompt on the workflow page that failed. Capture the page name, project name, and exact message before asking for help.
Deployment Workflow
Continue In This Workflow
Script preparation, translation workflow, live deployment, operator control, and runtime troubleshooting.
0.16 Error Messages & Troubleshooting
Decode common project, translation, deployment, auth, and operator-session issues.
2.1 Editor Quick Start
Use the core editor controls for languages, AI translation, simulation, and export.
4.5 Operator Quick Reference (ASM)
Use the operator cockpit to go live, advance cues, and handle show-time controls.