Understanding Queued, Failed, and Unknown States
Separate a confirmed terminal status from a page that simply stopped updating. Labels vary by service, and a spinner alone does not reveal what the provider is doing.
- Queued: The service reports that work is waiting. The label alone does not identify hardware availability or predict a start time.
- Processing: The service reports active work. It may include more than model generation, such as result retrieval or soundtrack processing.
- Confirmed failure: The service records a failed task. Read the recorded reason; it may differ from a browser's generic error.
- Unknown status: You cannot currently confirm the task outcome. A disconnected page may coexist with a server task that is still running.
Never automatically resubmit a job in an unknown state. If the original task remains active on the server, launching another task may consume additional credits and make reconciliation harder.
Differentiating Credit Releases from Payment Refunds
Understanding account balance adjustments prevents confusion when a render does not produce a finished file. Generative platforms treat internal credit balances and commercial billing transactions as separate accounting layers.
When a generation task encounters a confirmed failure, the platform automatically releases reserved generation credits back to your user account balance. Check the recorded balance adjustment before deciding what to do next; a visible error alone does not prove settlement has completed.
Payment refunds, by contrast, represent actual currency reversals for purchased credit packages or memberships. A credit release is handled automatically by the rendering scheduler, but payment refunds follow the separate refund policy and terms of service. Inquiries regarding monetary reimbursements must be directed to customer support rather than triggered through interface retry buttons.
Pre-Retry Diagnostic Checklist
Before re-uploading assets or starting a new generation cycle, review this diagnostic checklist to eliminate predictable submission barriers:
- Verify image formats and boundaries. As documented in the NEON DUO step-by-step workflow guide, input media must consist of two separate consenting adult photos in JPG, PNG, or WebP format, with each file staying at or below 10 MB.
- Confirm account authentication. Accessing private source photos and downloading completed video exports requires active owner login. An expired session may prevent you from reading status; signing in again does not itself resubmit a job.
- Review export specifications. Planned output files are structured as 15-second H.264 MP4 videos at 480p or 720p resolution, framed in either 16:9 landscape or 9:16 portrait orientation. Use supported form options rather than assuming an undocumented request will be accepted.
- Check interface constraints. Public creation templates use fixed motion reference models. The interface does not support custom text prompts or arbitrary external motion reference uploads.
- Inspect soundtrack status. The intended completion workflow waits for requested soundtrack processing before notification, though silent video files are retained internally. Note that template soundtracks are not verified official master recordings and do not include commercial synchronization licenses.
- Look for file integrity cues. A missing preview thumbnail or an unexpectedly small file export can serve as a clue indicating incomplete transfer, though neither provides definitive proof of stream truncation on its own.
Worked Diagnostic Example
To understand how input validation prevents failed retries, consider this worked hypothetical scenario (illustrative only):
Imagine two selected photos are 11.5 MB each, above the 10 MB limit. The creator sees a submission error. Their first action is to check whether a task ID exists and whether the account shows an accepted task or reservation—not to infer from the error that no work happened.
If no task was accepted and the files are identified as the issue, they can export smaller copies, check visual quality and retry when generation is available. If a task exists with unknown status, they record its ID and seek clarification first. The example describes a decision process, not a test result or a guaranteed successful second attempt.
Frequently asked questions
How can I tell if my generation is stuck or merely queued?
Check the recorded task while signed in. A queued status means the service reports waiting work; it does not provide a reliable completion estimate. If status remains unclear, contact support with the task ID and error details before starting another job.
Are generation credits returned if a render fails?
Yes. When the backend records a confirmed generation failure, reserved credits return to your account balance. However, this automated release of platform credits does not constitute a cash payment refund. Cash transactions are governed separately under the site's legal and billing policies.
Can I supply custom motion references or text prompts?
No. The standard template system utilizes fixed reference choreographies. The public web interface does not permit arbitrary motion video uploads or editable text prompts. For a broader perspective on template dance capabilities, read our broad overview of free neon dance creation.
Why does my finished video have no audio track?
First check whether you opened the retained silent version. The intended workflow adds the requested soundtrack separately and then notifies you. A failed audio stage needs its own status check; it is not a reason to automatically regenerate the silent source. No commercial music license is included.
Next Steps: Preparing Your Assets
While live generation and purchasing remain closed on this domain, you can prepare your input photography according to these verified technical standards. To explore available choreography styles, visit the complete directory of video guides or inspect the template creation interface.