What Should I Check When a Tethered Product-Photo Session Disconnects Halfway Through a SKU Batch?

Stop the sequence and preserve both sides of the connection

When the camera disconnects, stop downstream automated processing and record the last confirmed capture identity. Do not immediately reset the filename counter, clear the destination folder or delete images from the camera.

The gPhoto2 project documents separate operations for camera capture, file-added notifications, downloading and keeping or deleting camera-side files. That separation explains why a disconnected session cannot be reconstructed from host filenames alone.

Record the planned SKU and view sequence, the capture application's log and the host files actually present. If the camera remains accessible, inspect its file list through supported controls without changing the originals.

A camera-side capture-complete event is not the same as a confirmed host download. Conversely, a completed host file does not prove that the next planned angle was ever photographed.

Build a three-state reconciliation ledger

For every planned product view, distinguish three questions: Was the camera triggered? Does the camera retain the file? Was a complete host copy received?

Use actual source identifiers, not just sequence numbers. Compare capture timestamps, camera filenames and visible product angles where available. Filename order can be misleading after a reconnect or counter restart.

Classify each planned view as confirmed received, captured but not yet retrieved, not captured or unresolved. An unresolved state should remain unresolved until source evidence supports a decision.

If a camera file exists but no complete host copy is present, retrieve that specific source through the capture application's supported download workflow. If neither source nor reliable capture evidence exists, recapture the missing view with the same approved product and setup.

Do not assume that every reconnect operation automatically imports images captured during the interruption. That behavior depends on the actual tethering application and camera configuration.

Hypothetical four-view bottle sequence

Hypothetical illustration—not an executed tethering recovery: a fictional bottle SKU B12 requires front, left, back and right views.

The front and left files are stipulated to have reached the host successfully. The camera disconnected after the back exposure. The back image is stipulated to remain on the camera, while the right exposure was never taken.

The proposed recovery is to preserve the two received files, retrieve the existing back image and capture only the missing right view. Restarting all four positions without reconciliation would create unnecessary duplicates and might obscure which source belongs to the approved sequence.

If the camera's back image is unreadable or depicts an incorrect angle, that row remains unresolved. Its existence alone does not satisfy the required view.

The worksheet is a fictional planning record, not a report of actual recovered files.

Resume from a verified state, not a guessed counter

Before resuming automation, confirm the camera connection, output directory, naming policy and current product position. Verify that a newly received test file can be transferred completely without overwriting an earlier source.

Use a session-qualified filename or ingest identifier to distinguish resumed captures from the original sequence. Preserve original camera names for traceability.

Then resume only the planned positions that remain genuinely missing. Compare the resulting contact sheet with the approved shot list and the real product's orientation.

If the camera or capture application deletes camera-side files after download, review its documented retention settings before proceeding. gPhoto2 exposes relevant keep and no-keep options, but their availability and behavior depend on the supported capture mode.

Close the session when every required view has one verified source identity, complete host copy and appropriate product-state review. A recovered file is not automatically a visually approved product photograph.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• gPhoto2 — Official command manual: Documents capture, download, event waiting and camera-file retention controls.
• libgphoto2 — Camera event definitions: Establishes distinct camera file-added and capture-complete event types.
• libgphoto2 — Tethering example: Illustrates explicit download and camera-file operations after camera notifications.