Resume by locating the existing task and its actual status before starting another generation. Draft inputs, a submitted job and a downloaded result are different states. A browser refresh may lose a local draft without cancelling a server task. Changing devices also does not prove that a task failed or needs resubmission.
Know which state you are recovering
A draft contains intended inputs but may never have been submitted. A submitted task has an identifier and status. A completed task has a result to inspect. Record the task identifier through the site's visible workflow where available, and keep an approved output copy for important work.
Do not assume browser-local draft storage synchronizes across devices. Also do not copy authentication cookies or other login data between machines. Sign in through the authorized normal flow and use the account's supported task and library screens.
A fictional interrupted poster job
An invented creator submits a poster and closes the tab. On another device the creation form is blank. Pressing Generate with the same source would create another task, not restore the old tab. The first action should be checking the account's existing jobs and locating the original submission.
If the job is complete, review and download its result. If pending, inspect its visible status. If failed, keep the task details and follow the appropriate retry or support path. Do not infer failure merely from an empty form or missing local preview.
Recover without creating duplicates
Check the currently signed-in account. Use the task list, any visible task identifier and the actual result status. Compare timestamps and input purpose if several tasks look similar. Avoid exposing private task links or assets publicly in a troubleshooting request.
If the task cannot be located, record what is known and contact support with the relevant non-secret details. An uncertain submission should remain uncertain until reconciled. Repeated clicking is not a reliable diagnostic and may create additional charges if separate tasks are accepted.
Keep an intentional project handoff
Imagild's task and library workflows can help locate account-owned results. Use only features confirmed in the current interface; this guide does not promise universal autosave or cross-device recovery of every form field. Store your plain-language brief, source permission and approved file separately when the project matters.
For a longer film, distinguish the project story, each individual shot job and the assembled export. Recovering one clip does not prove the complete film was exported. Inspect those states independently before continuing production.
Does refreshing cancel generation?
Not necessarily. Check the actual task state. The browser display and server task lifecycle are separate.
Can I reopen the same task from another account?
Do not assume so. Tasks and assets have ownership boundaries. Use the authorized account and its supported access paths rather than treating a copied URL as permission.