· reAPI Team
Hotel Lobby AI troubleshooting: templates and exports
Troubleshoot Hotel Lobby AI by stage: reference access, photos, submission, polling and soundtrack export. Keep your task ID and avoid unnecessary new requests.

Hotel Lobby AI troubleshooting starts with identifying which step stopped. A template that will not download, a rejected submission, a task still processing and a completed silent video waiting for its soundtrack need different fixes. The reAPI tool separates video generation from soundtrack export, so an audio error is not a reason to assume the video must be generated again[1].
This guide covers the orange-studio duet made from two identity images and a motion reference. It does not claim to repair another site's download service or diagnose a hidden provider error. Preserve the task ID and the original error detail before changing anything. Those facts tell you more than repeating the same request.
TL;DR
- The reAPI preset already includes a line-art motion reference. You do not need to download that reference and upload it again for the default tool workflow[1].
- A browser preview is useful, but a remote generation request also needs accessible media URLs. Keep image inputs and the motion-video input in their correct roles[1].
- A task ID means the request was accepted for processing; it does not mean generation finished. Check that task before submitting a replacement[2].
- The current tool checks status on a two-second interval with a generation polling ceiling of roughly thirty minutes. That is browser behavior, not a delivery-time promise[2].
- If the original video completed and only soundtrack export failed, retry export for that task. The retry reuses the existing video; an uncertain audio submission needs verification[3].
Find the failed stage before choosing a fix
Use what you can actually observe. Do you have an input preview? Did submission return a task ID? Is the task terminal? Is the missing result the video itself or the version with audio? A useful Hotel Lobby AI troubleshooting note records those answers before anyone tries again.
| What you see | Stage to inspect | Next action |
|---|---|---|
| Reference cannot be downloaded or previewed | Reference access | Confirm the asset location and whether you need a local copy at all |
| One identity image is missing or wrong | Input preparation | Replace that image before submitting |
| Submission fails without a task ID | Submission | Keep the original error and check the request or sign-in state |
| Task ID exists but the result is pending | Generation and polling | Check the same task; do not create a duplicate just to refresh progress |
| Original video completed; soundtrack export failed | Audio export | Reuse that video with the export retry |
| Download is silent | Output selection and playback | Confirm whether it is the original video or the final file with audio |
These categories are not diagnoses of an unknown error. They narrow the next check. If you cannot tell whether a request was accepted, preserve the response and ask for the task status to be verified rather than assuming that a retry is harmless.
Hotel Lobby AI templates: download and access are separate
The default Hotel Lobby AI tool includes a preview of its line-art reference and passes the motion reference to the selected model. The template is already part of the request preset. For that workflow, downloading a separate local template is unnecessary[1].
A question reported under a Kapwing tutorial about downloading its template motivated this part of the guide. It is an attributed user question, not evidence that reAPI has the same download failure. We have not reproduced that service's error, and this article does not provide a workaround for its account or download controls.
When preparing another reference workflow, distinguish three locations: the page that shows a video, the media file itself and any local copy on your computer. A webpage URL is not interchangeable with a direct video URL. A local path that your browser can read is also not a public address a remote generation service can fetch.
For a direct media reference, check that the URL points to the intended file and remains accessible without your browser's private session. Preserve the original asset rather than repeatedly saving a compressed screen recording. If a reference is rejected, inspect the actual message and the selected model's input documentation before changing resolution, duration or format blindly.
There is no supported rule here that says “upscale the template and every low-quality error disappears.” A reported quality rejection can have several unknown conditions. Check what the request actually sent. If you use the default reAPI preset, first confirm that the preset reference remained in the video field and that an advanced override did not replace it.
Keep the photos and motion reference in the right roles
The tool's default mapping is explicit: first image for the left performer, second image for the right performer, and video reference for motion. The preset prompt asks the model to preserve appearance from each image while following choreography from the reference video[1].
Before submission, look at each identity image separately. Does it contain the performer you intend? Is there an unwanted second person? Is the body shape or clothing visible enough to explain the appearance you want? A group portrait in both slots does not express the same instruction as one clear identity per slot.
A correct mapping is still not a guarantee of perfect hands, identical faces through every turn or frame-accurate motion. If a completed result has an identity or motion problem, that is a quality review of the result, not necessarily a failed request. Note the exact moment that needs improvement so a future version changes something purposeful.
Read the prompt and reference guide for image order and instructions. For animal inputs, consult the pet pose and motion guide. Do not assume that an ordinary pet photograph defines an upright performance pose.
The article cover is conceptual character artwork. It is not a tested output, a quality benchmark or proof that the displayed figures can be reproduced by the current preset.
Submission errors and accepted tasks need different responses
If the tool asks you to sign in, finish that step before trying to submit. If an image upload fails, resolve the upload or use an accessible image URL. If additional parameters are invalid JSON, fix the JSON before generation. Those are preparation or submission issues; they are not evidence that a server-side video failed[1].
When a request is accepted, its task ID is the reference for subsequent checks. Acceptance means processing can begin. It does not verify every requested setting's visual effect and does not guarantee that the final result will be usable[2].
Keep the following with any support request:
- The task ID, if one was returned.
- The selected model and the time you submitted.
- The duration, resolution and relevant advanced settings.
- Whether you saw a completed original video.
- The original error message and error code, where available.
The tool displays a localized explanation for recognized network or polling issues and keeps the original error in an expandable details section. That detail matters. A generic generation message should not be interpreted as proof of a balance problem, moderation rejection or unsupported parameter without the actual error evidence.
Avoid posting private keys or account credentials with those details. The task ID and error record are useful; a credential is not necessary for someone to understand which stage stopped.
A polling timeout does not prove that generation stopped
The current generation hook normally checks every two seconds. The Hotel Lobby tool allows up to 900 generation polling attempts, corresponding to a nominal thirty-minute interval budget. Requests and browser scheduling can add time, so this is not an exact wall-clock deadline. More importantly, the ceiling limits the browser's status checks; it is not a promise about when a video will be delivered[2].
A network error can interrupt those checks. A polling-limit message also describes the status-checking process. Neither alone establishes that the server has cancelled the task or that billing has settled. Keep the existing task ID and inspect that task's current status before creating another request.
One recorded Seedance 2.5 draft run on October 10, 2026, took 648.2 seconds from the recorded start until completion. It used a 15-second, 480p request with two prepared identity images and the motion reference[4]. That is a single observed run, not a normal waiting time, a benchmark or a guarantee for other models and inputs.
Do not use that observation as a countdown. A slower run needs a status check, not an assumption that it has failed. A faster run does not prove that a future request will be equally fast. If you are reviewing a billing concern, read the actual task record as described in the cost and one-time-use guide.
The video can finish before the soundtrack is ready
The default generation request has generated audio disabled. The public video-generation result is therefore the original video, while the tool prepares a separate final version with the template soundtrack. Simply enabling model-generated audio is not equivalent to restoring that existing soundtrack[1].
During export, keep the two outputs distinct. A completed original video means generation has succeeded. A later export error means the soundtrack step needs attention. The tool's soundtrack retry uses the completed task ID and the original video rather than submitting the entire performance again[3].
If export is still processing, allow that stage to finish. If it fails, use the export retry. If the response says the audio submission needs verification, contact support with the video task ID. The implementation preserves an uncertain submission instead of blindly starting another processing request, because a timed-out submission might already have been accepted[3].
Here is the recorded example after its soundtrack was added:
Recorded Seedance 2.5 draft with template audio. The poster shows the motion reference, not the generated output.
The saved media inspection found no audio stream in the original, and an AAC audio stream in the combined example[4]. This supports the distinction between the files. It is one recorded result, not a guarantee that every new soundtrack export will succeed.
If a file seems silent, check playback volume and confirm which file you downloaded. The original generation and the file with the soundtrack are different assets. Users of the public generation API should not assume that its original output includes the tool's post-generation template audio.
Questions about templates and failed generations
Must I download the template before using reAPI?
No. The default tool preset already includes the motion reference. A different workflow may need its own accessible media file, but that is a separate preparation choice.
Does a low-quality reference error mean I should upscale everything?
Not automatically. Read the original error, confirm the file actually submitted and check the selected model's input requirements. We have not reproduced another site's reported rejection.
What should I do when a task ID exists but no video appears?
Keep the ID and inspect the same task's status. A task can be accepted before it completes. Do not repeatedly submit just to see whether a second request is faster.
Is the thirty-minute polling budget a delivery promise?
No. It describes the current browser checking behavior. It does not guarantee completion within that time or establish that the server task ends when polling stops.
Why is the public API video silent?
The preset disables generated audio. The tool adds the template soundtrack after generation; that post-processing step is separate from the original public API output.
Should I regenerate when soundtrack export fails?
Use the export retry for the existing completed task. It reuses the original video. If the audio submission is uncertain, preserve the ID and request verification.
Does a visible error prove the task was refunded?
No. An input error, a browser network interruption, a terminal video failure and an audio failure are distinct. Check the task's status and billing record.
What information helps support investigate?
Keep the task ID, model, settings, submission time and original error details. Say whether the original video completed and whether the missing part is the soundtrack export.
Resume the step that actually stopped
When your inputs are ready, follow the complete creation tutorial. If something fails, preserve the existing evidence before changing settings or starting again. Hotel Lobby AI troubleshooting works best when you check the original task and repair the interrupted stage, especially when a completed video only needs its soundtrack export.
References
- reAPI. Hotel Lobby AI preset and studio. Implementation reviewed October 10, 2026. reapi.ai/tools/hotel-lobby-ai.
- reAPI. Task acceptance, status and results. Implementation reviewed October 10, 2026. Tasks API documentation. Polling intervals and limits describe the current tool behavior.
- reAPI. Hotel Lobby AI soundtrack export and retry. Implementation reviewed October 10, 2026. Tool and export controls. Uncertain submissions require verification.
- reAPI Team. Recorded Seedance 2.5 draft generation, audio export and media inspection. Observed October 10, 2026. Public run record.