> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/help/troubleshooting.md).

# Troubleshooting

Find help for upload failures, missing assets, incomplete renders, and download problems.

## Uploads and scene preparation

| What you see                                                                               | Where to check                                                                                                                                        |
| ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Upload scene** is unavailable, a file is rejected, or the scene shows **Upload Failed**. | The [upload guide](/docs/web-app/upload-scenes.md#if-an-upload-does-not-work) covers the credit requirement, accepted files, and interrupted uploads. |
| A scene shows **Failed** or **Requires Review** after uploading.                           | Check [scene preparation failures](/docs/web-app/upload-scenes.md#if-an-upload-does-not-work).                                                        |
| Textures, linked models, or other assets are missing from the render.                      | Check the files included in your upload with [Before you upload](/docs/prepare-your-scene/overview.md).                                               |
| A simulation or animation renders differently from the one on your computer.               | Check [simulation caches](/docs/prepare-your-scene/caching-simulations.md) and whether the required cache files were included.                        |
| A scene shows **Expired**.                                                                 | [Upload the source file again](/docs/web-app/upload-scenes.md) before creating another job.                                                           |

## Rendering and review

| What you see                                                  | Where to check                                                                                                                                                                                               |
| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Create Job** cannot be submitted.                           | Check the required choices and highlighted fields in [Create a job](/docs/web-app/create-a-job.md).                                                                                                          |
| A job is queued or a frame seems to have stopped progressing. | [Track progress](/docs/web-app/track-progress.md) explains the statuses. For a frame already assigned to a node, see the options in [Review and approve frames](/docs/web-app/review-and-approve-frames.md). |
| A job has stopped with failed or incomplete frames.           | See [duplicating a job with incomplete frames](/docs/web-app/manage-jobs.md).                                                                                                                                |
| A rendered frame has a visual fault.                          | Check [review and re-render options](/docs/web-app/review-and-approve-frames.md) before approving it.                                                                                                        |
| The expected pass or file format is missing.                  | Check [render passes](/docs/web-app/render-settings.md) and the job's [output configurations](/docs/web-app/outputs.md).                                                                                     |

## Downloads and finding work

| What you see                                                             | Where to check                                                                                                                                                                   |
| ------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The render is finished, but outputs are unavailable.                     | Check whether its frames still [need approval](/docs/web-app/review-and-approve-frames.md).                                                                                      |
| A job shows **Expired**.                                                 | Its outputs can no longer be downloaded. See [job management](/docs/web-app/manage-jobs.md) for rendering again.                                                                 |
| Files are not arriving in your chosen folder.                            | Check the destination and folder access in [Download frames](/docs/web-app/download-frames.md), or the connection in [Deliver to cloud storage](/docs/web-app/cloud-storage.md). |
| Folder access, video creation, or desktop notifications are unavailable. | See [Browser support](/docs/help/browser-support.md).                                                                                                                            |
| You cannot find a scene, job, or project.                                | Use [Search](/docs/web-app/search.md), including search by ID when you have it.                                                                                                  |

If the problem continues, [contact support](/docs/help/get-support.md) with the affected scene or job and the error message.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://know.rendernetwork.com/docs/help/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
