SnapCircle 360
  1. SnapCircle 360
  2. Guides
  3. Capture

A clip hasn't finished processing: what to check

First find the last completed stage: recording, processing, local save or cloud delivery. Check the correct event and any visible job status before assuming the video is lost. Preserve available copies, pause new recordings if unfinished work is accumulating, and investigate the stated error. A finished clip waiting to upload needs a different response from a recording that has not produced an export.

Identify the symptom precisely

“The video has not appeared” could mean several things. The operator may be looking in another event, a job may be waiting behind an earlier recording, or the finished clip may already be local while cloud delivery remains pending.

Start with the event reference, approximate recording time and chosen take. Then use the table to narrow the next check. These are diagnostic categories, not labels that every booth app displays.

What you can observe What it suggests Next useful check
Clip absent from the event you opened Wrong location or unfinished processing Confirm event, recording reference and job list
Job is waiting It has not started its processing turn Inspect earlier jobs and current queue state
Job is processing Export work has started Watch for completion, a changed status or an error
Job reports failure A specific operation did not complete Record the message and preserve available source footage
Finished clip plays locally but no link exists Capture and export succeeded; delivery is unfinished Inspect the selected provider and upload status
Link opens but recipient cannot download Recipient access or delivery problem Test the actual link from the recipient's position

Do not redo capture merely because a QR is unavailable. If the correct finished clip plays locally, the investigation belongs with delivery. The QR sharing guide covers that branch.

Distinguish a delay from a failed job

There is no useful universal timeout for a booth export. The device, recording, effect and outstanding work affect the comparison. Use your own successful rehearsal with the same configuration as context, not an invented promise that processing always finishes in a fixed number of seconds.

Look for evidence of progress where the app exposes it, and note when the state last changed. A job waiting behind another job is different from an active job that reports an error. Repeatedly pressing controls can make the record of what happened less clear, even when it does not fix the cause.

Bring the app to the foreground to inspect the work. On-device processing does not imply unlimited execution while an app is backgrounded; iOS controls background runtime. Apple's background execution guidance explains that limitation. Do not promise that locking the phone will let every pending export finish unattended.

Preserve what exists before changing anything

Check for a playable raw recording in the location where your workflow saves safety copies, and a playable processed version in the event gallery. Record which you found. A thumbnail is a lead to inspect, not proof that a complete usable video is present.

If you cannot find the recording, a pending job or a saved copy, record that gap for support. Confirm the event and device involved, but do not promise recovery merely because someone remembers pressing Record.

Do not delete the event, reinstall the app or erase files as a first troubleshooting step. Those changes can remove evidence or the remaining copy. If you need to free space, distinguish unrelated verified content from current unfinished work.

In SnapCircle's documented workflow, a raw Photos save is attempted before processing. After successful processing, its internal raw working file is removed. A later raw safety copy therefore depends on that Photos save succeeding. A processing problem does not justify promising the raw recording will always be recoverable, and the app gallery is for processed clips.

Check the condition named by the error

If the message concerns space, inspect device storage and the unfinished workload. Settings → General → iPhone Storage is the starting point; deleting an app also removes its related data. Apple's storage guidance explains the distinction. More cloud allowance does not directly create working room on the phone.

If a temperature warning appears, stop and follow Apple's temperature instructions. Do not try to force a delayed export through a device warning.

If the job refers to unavailable input or an export failure, keep the exact message and the available files. If your installed app offers a retry, first address the reported condition and use the documented control. A retry needs usable input and is not a guarantee of recovery. Avoid repeatedly changing the event treatment while trying to understand one failed job.

For recurring problems, compare the affected configuration with the last known successful one. The booth phone guide explains how to separate device, capture and processing constraints without assuming a new handset solves every delay.

Give support evidence it can act on

Collect a short incident record rather than sending only “processing is broken”:

  • Phone model, iOS version and app version.
  • Event and clip reference, approximate time and visible status or exact error.
  • Raw recording length, resolution choice and effect.
  • Available device storage and any device warning.
  • Whether a raw Photos copy or finished local clip exists and plays.
  • What changed before the issue and what you have already tried.

Use a screenshot of the error where helpful, without exposing unrelated guest footage or account details. If support asks for a reproduction, use a neutral test subject after preserving the event's files. Do not present a successful new test as proof that the earlier recording has been recovered.

Use the next action that matches the stage

SnapCircle 360 separates an on-device processing queue, the processed event gallery and optional Dropbox or Google Drive uploads. That separation helps an operator ask a specific question: is the output still being created, or is the output ready and awaiting delivery?

If you are evaluating this workflow, download SnapCircle and rehearse capture through finished-file delivery. Operation requires a subscription. Keep the rehearsal configuration and outcome as your comparison point, then diagnose an interruption from observed stages rather than guessing that every missing link is a failed recording.

Published 19 November 2026. Guidance is based on documented capabilities and an operator checklist. Test your own equipment before a booking.