OurDream generation errors: refunds and safe retries

Editorial note: This article uses public documentation and editorial analysis. We have not completed hands-on testing of the products discussed. Our methodology Disclosure

By Daniel Kraus

If an OurDream image or video fails, stop before submitting the same job repeatedly. Identify the error, check whether the job actually failed, and compare your Dreamcoin balance with the amount recorded before the request. A stalled preview and a completed charge are different observations.

This guide uses official documentation checked on October 3, 2026. We have not deliberately triggered failures or measured refund times in a paid account. The incident worksheet and examples below are original troubleshooting aids. For the broader product decision, see our OurDream review.

Identify the error before choosing a next step

OurDream’s generation-error guide distinguishes timeouts, server errors, policy violations and insufficient Dreamcoins. It describes automatic coin returns for failed jobs. For repeated timeouts it suggests a simpler request; server errors call for waiting before retrying. A policy flag calls for checking the rules and removing prohibited material, not trying to evade moderation.

Separate the symptom from the conclusion
What you observe	What to record	What it does not establish
The page is still waiting	Whether the job history has a final status	That the job failed or that another submission is safe
A failure message appears	The exact message and job time	That every later balance change belongs to this job
The result exists but is disappointing	The completed result and the original objective	That a documented failed-job coin return applies
A low-balance warning appears	The quoted cost and available balance	That buying more will resolve an unrelated service error

Use an exact error label in your notes. “It broke” does not distinguish an upload problem, a rejected prompt, an unfinished job or an unavailable result. Avoid sending several different jobs while you investigate: each extra transaction makes the balance harder to reconcile.

Check the coin return as a separate event

The official guide says to allow up to 15 minutes before escalating a missing failed-generation coin return, then refresh and check the history and balance. It asks users to contact support with the failure time if the balance is still wrong. That is the provider’s stated process, not a response-time guarantee from us.

Write down the balance before the job, the displayed price, the balance after the attempted charge and the balance after any return. If another task ran in between, give it its own row. A balance that remains lower can reflect another completed request; a restored balance does not prove the failed result became usable.

Illustrative ledger, not an OurDream price quote or test result
Event	Example balance	Interpretation
Before a fictional 20-credit job	300	Starting point
After charge	280	20 credits deducted
After recorded return	300	The deduction reconciles if no other transaction occurred

Substitute the actual displayed numbers. Do not convert Dreamcoins to cash using an assumed fixed rate: your allowance, pack purchase and subscription are different inputs. A coin return for a failed task is also different from a refund of a payment.

Make one controlled retry when appropriate

Preserve the error text, timestamp and any job identifier.
Wait for the previous job to reach a final state and check the balance.
If the error is technical and the provider recommends retrying, use a small permitted request.
Change one variable only, such as simplifying the scene.
Record whether the new job completes and what it costs. Stop again if the failure repeats.

For an original non-explicit diagnostic scene, describe a fictional adult reading beside a window, with one subject and one simple background. The purpose is to reduce variables, not to promise that a particular prompt fixes a server fault. Do not add sensitive reference material just to see whether a service is working.

“One controlled retry” is our suggested stopping rule, not a documented OurDream quota. It keeps a short investigation from becoming an open-ended spending session. A successful simple image still does not establish that the original video workflow is functioning.

Distinguish chat problems from media problems

OurDream has a separate chat-response troubleshooting page. It advises allowing a response time, avoiding rapid repeated messages, checking the relevant model’s coin requirement and trying a fresh browser session when appropriate. These are chat checks; a reply appearing in chat does not confirm that an image-generation job completed.

Use a simple isolation grid: does the account load, does an ordinary text exchange work, and does one permitted media task finish? Record “not checked” for anything you did not try. You do not need to delete a character or clear its history to gather those observations.

Prepare a useful support note

Use the official support route linked from your account. Include the task type, date and time with time zone, visible error, affected character or job identifier, balance observations and the single retry you attempted. A cropped screenshot can show the relevant UI without exposing the rest of a conversation.

Do not send a password, payment-card number or unrelated private transcript. Keep your own copy of the report and its reference number. If the issue concerns a completed result’s quality, say so directly instead of describing it as a failed job.

For choosing a workflow and defining an acceptable result before spending, return to our image-generator buying guide or video-generator guide. The useful outcome is a clear diagnosis and a bounded next step, not a larger number of retries.