Read before this
Read these direct prerequisites in order. Each guide lists any earlier context it assumes.
Before you start
Keep the exact conversation, editor, or Tool-result URL and the last visible status. Check the active account or team, plan, credits, browser, and approximate time before retrying a potentially expensive operation.
Why time varies
- Video length and number of scenes
- Source collection and Deep Research
- Selected text, image, and video models
- Narration, music, transitions, and media processing
- Current system demand
You can leave and return
Agentic runs use durable workflow and reconnection behavior. You do not need to keep the same page continuously visible. Reopen the conversation from Recents or Projects to restore its current status and continue when the workflow completes or needs input.
Recover a stalled or failed run
- Reopen the exact conversation and read the latest visible status.
- Check whether the run is waiting for approval, a source, a voice, or more credits.
- Use the visible retry or recovery action when one is offered.
- Retry the failed scene or operation instead of restarting a good project from zero.
- Review Usage before repeating an expensive generation several times.
Contact Support
Contact Support when there is no visible state change for an extended period, recovery repeatedly fails, or the output is missing after a completed status. Include the conversation or project URL, approximate timestamp, last visible message, browser, and whether a retry was attempted. Never send passwords or API keys.
Keep going
Find, reopen, filter, rename, and delete work in the current Projects experience.
Understand credit estimates, reservations, charges, plan grants, top-ups, and auto top-up.
Use the current Usage page to understand credit activity and investigate unexpected charges.
Download an MP4 from an agentic video or editor project at the current plan resolution.