Check the existing task before submitting another one. A page that stops showing progress does not necessarily mean the provider stopped working. Record the job identifier, inspect its current status and look for a delivered result. Retry deliberately after you understand the state, rather than using repeated clicks as a progress indicator.
Distinguish the browser from the generation task
A browser can lose a connection while a server-side job continues. Conversely, a submitted task can fail before producing a file. Those situations may look similar in a spinner but require different next steps. Reopening a page is not the same as starting a new generation.
Use the task view in Imagild when available to inspect the job that already exists. Check its timestamp, media type and selected workflow so you do not confuse a previous attempt with the current one. Never infer completion from elapsed time alone.
| What you can verify | Sensible next action | Avoid |
|---|---|---|
| A queued or running task exists | Keep its identifier and check that task | Repeated duplicate submissions |
| A completed result is available | Open and review the actual file | Paying for another take because a thumbnail was slow |
| A clear failure is recorded | Read the visible reason and correct the input | Resending the unchanged request indefinitely |
| Status remains uncertain | Contact support with the job identifier | Assuming either success or a refund |
Collect a small, useful support record
Example support note: the image task submitted at approximately 14:20 is still marked as processing. I refreshed the page once but did not submit another request. The job ID is the one shown in Jobs. Please confirm whether it is still active before I retry. The workflow was Fan Merch and the selected output was 2K.
Use your actual details, not the example values. Do not include API keys, login codes or unrelated private photographs in a public message. A screenshot of the relevant task and its visible error can help, but review it for private information first.
Review points separately from the progress label
The available balance can reflect a reservation while a task is active. A failed result, an uncertain provider submission and a completed output can follow different reconciliation paths. Check the displayed transaction or support response instead of assuming that every browser error means a permanent deduction or an immediate reversal.
The current pricing page describes the public charging model. This guide does not promise a fixed processing time or invent a universal refund deadline. For your specific task, the recorded state and confirmed accounting outcome matter.
Make the next attempt diagnostic
If a retry is appropriate, change the part related to the failure: an invalid upload, an unsupported selection or an overcomplicated action. Keep a note of what changed. If the first task is merely slow, do not create a second one just to compare which finishes first.
Can I close the browser while a job runs?
Do not use an open tab as your only record. Keep the task identifier and revisit its status. Closing the browser is not a cancellation request.
Where do I inspect a task?
Open Jobs while signed into the account that created it. Your private job history is an account feature, not a public page that search engines should index.