# Upload, Generation, and Export Failures Source: [Upload, Generation, and Export Failures]() Documentation index: [llms.txt]() Last updated: 2026-10-28 When Seedance or another generation fails, distinguish local validation, supplier rejection, transport timeout and failure of an already-created job. Preserve the project and exact error, check whether a job exists, then decide whether to retry. A timeout does not establish a model limit. Check Credits History for actual charges rather than inferring billing from the failure state. | Symptom | Check first | Recovery | | --- | --- | --- | | Imported asset fails or never becomes ready | File opens locally; type is listed in Supported Formats; upload is complete | Preserve the project and original files, then follow the manual-import guidance below before retrying. | | Generation does not start | Confirmation card, credit balance, model input slots, plan gate | Approve or adjust the request, remove incompatible inputs, or choose an available model. | | Generation asset shows Failed | Its My Assets card and AI message | Ask the AI to regenerate only after correcting the likely input or service issue. Check Credits History before assuming a charge. | | Export is disabled | Active Timeline has content; required captions or graphics exist | Add a clip, finish transcription, or switch to an export tab that matches the Timeline content. | | Export remains at Preparing media | Source uploads are still running | Let source uploads finish, then check the same export’s status. If it remains blocked, preserve the project and report its current status. | | Export fails | Queue row and network/local destination state | Select **Retry**. For Desktop local export, verify destination access and free disk space. | ## Manual import, unavailable media, and Agent credits Importing media and editing the timeline by hand do not use credits. Asking the built-in ChatCut Agent to edit uses credits, even when you supply your own footage. See [Plans and Credits Overview](https://pr-689-preview.chatcut.dev/docs/plans-and-credits). An Agent credit warning does not explain a separate **Asset unavailable** or **Relinking** state. Note whether the message appears in the Agent chat or on the media itself. Buying credits is not a recovery test for unavailable media. Keep the existing project, original files, and browser site data while investigating. Before clearing site data, deleting or recreating the project, or repeating import/relink attempts, report the problem through **Feedback** or [team@chatcut.io](mailto:team@chatcut.io). Include the project name, approximate time, browser or ChatCut version, exact messages, and screenshots showing where progress stops. These symptoms alone do not establish the cause or a confirmed recovery. ## Export says “0 B available” but my drive has free space First identify where the export is rendering. A browser-rendered export can use the browser’s storage allowance for the site; that is different from the total free space shown for a drive. Desktop local video export writes to a selected destination. Free space alone does not establish which limit caused your error. See [Web vs Desktop Export](https://pr-689-preview.chatcut.dev/docs/web-export-limits). - Keep the exact error text, export type, ChatCut version and operating system. If the job is still listed under **Export**, capture its current status before closing the app or tab; the queue is not a permanent history. - For Desktop local video export, use **Export → Video** and choose a destination when prompted. Check that you can write to that folder. Agent exports use the returned `outputPath`; see [Desktop Local Export](https://pr-689-preview.chatcut.dev/docs/desktop-local-export) for the distinction. - If no destination prompt appears or the same error persists, report that with the screenshots through **Feedback** or [team@chatcut.io](mailto:team@chatcut.io). Do not repeatedly start a long export without a changed condition. Preserve your project and original media before clearing any site data. A long elapsed wait is not an estimate of the time remaining. Include when the job started and whether it is still present, failed, or disconnected; support can then distinguish the reported symptoms without guessing a cause. If the same valid job fails again, collect the project name, approximate time, visible error text, asset or export type, and the matching Credits History entry. Use **Feedback** from the avatar menu or email [team@chatcut.io](mailto:team@chatcut.io). See [Common Errors](https://pr-689-preview.chatcut.dev/docs/error-messages), [Supported Formats](https://pr-689-preview.chatcut.dev/docs/supported-formats), and [Export Queue, Downloads, and Retries](https://pr-689-preview.chatcut.dev/docs/export-history). ## Seedance 2.0 not working: identify the failing stage ### Last verified: October 28, 2026 | Fact and scope | Finding | Source | | --- | --- | --- | | Local 4K validation | Full Seedance 2.0 documents native 4K; ChatCut blocks it pending pricing, not because the model lacks it | [Official API](https://docs.byteplus.com/en/docs/ModelArk/create-video-generation-task-api), [pricing rationale](https://github.com/ChatCut-Inc/chatcut/pull/5569), [verification scope](https://pr-689-preview.chatcut.dev/docs/workflow-failures#verification-scope) | | Endpoint connection timeout | Ark probes received no HTTP response; 4K acceptance remains unverified | [Verification scope](https://pr-689-preview.chatcut.dev/docs/workflow-failures#verification-scope) | | Reference mode | 2.0/Fast/Mini audio references require an image/video; frames cannot mix with reference mode | [Official API](https://docs.byteplus.com/en/docs/ModelArk/create-video-generation-task-api) | | 2.5 task creation | A created task can later fail with TaskTypeMismatch or TaskTypeConstraint | [Official API](https://docs.byteplus.com/en/docs/ModelArk/create-video-generation-task-api), [2.5 tutorial](https://docs.byteplus.com/en/docs/ModelArk/seedance-2-5) | | Billing | Estimates and settlement differ; check matching ledger entries; no blanket failure-refund promise | [Credit policy](https://pr-689-preview.chatcut.dev/docs/credits-policy), [generation credits](https://pr-689-preview.chatcut.dev/docs/generation-credits) | | Stage or symptom | Check first | Next step | | --- | --- | --- | | Parameter error before a job exists | Exact version, resolution, duration, count and reference combination | Correct that setting; full 2.0 4K requires ChatCut pricing integration | | Supplier cannot fetch a reference | Completed upload, file constraints, public URL reachability/expiry | Retry after access changes; your browser opening a file does not establish supplier access | | Moderation or small-input rejection | Exact error, file dimensions, authorization and route rules | Correct that input or contact support; do not turn moderation into a permanent model-capability claim | | Timeout or disconnect | Existing asset card, task ID, progress or completed output | Check the same job before submitting again to avoid duplicate work | | Failure after task creation | Final task state and exact supplier error | For 2.5, check agreement between prompt intent and edit/extend mode | | Unexpected charge | Matching Credits History estimate/settlement and separate Agent usage | Send support the time and error; an account-wide balance change is not this job’s charge | 1. Keep the project, original assets, version and full error; do not begin by deleting or recreating the project. 2. Check the asset card or task progress to learn whether a job was created. A transport timeout is not a final job state. 3. Use [reference rules](https://pr-689-preview.chatcut.dev/docs/generation-references) and the [capability matrix](https://pr-689-preview.chatcut.dev/docs/model-capability-matrix) to correct the actual mismatch. 4. Check the same job and ledger before retrying. If the recovery condition is unclear, send the record through Feedback. ## Frequently asked questions Why did Seedance 2.0 generation fail? Identify the stage: local parameter validation, reference fetching, moderation, transport or an already-created job. Preserve the exact error. One failed request or timeout does not establish a missing model capability. What does a moderation or small-input error mean? Check the exact route error, source dimensions, file constraints and authorization. Moderation and file validation are different stages; follow the route rules rather than assuming a universal model limitation. Was a job created despite the timeout? A timeout alone cannot answer that. Check the existing asset card, any task identifier and progress for the same job before deciding to submit again. ## Sources and verification scope Last verified **2026-10-28**; native documentation accessed **2026-10-27**. Integration findings come from the internal source/receipt audit of product beta `b3cbb24d`. Ark checks timed out at connection level; this is neither supplier rejection nor successful generation. These are diagnostic steps, without new production examples for every error or a verified universal refund policy. See [Desktop local export](https://pr-689-preview.chatcut.dev/docs/desktop-local-export#native-upscale-export).