Troubleshooting Uploads And Processing

• Confirm the file type is supported by the workflow.
• Check whether the file is empty, corrupted, or still being written by another program.
• Retry failed items from the upload queue.
• For large files, allow multipart upload to complete before closing the browser.
• If direct browser upload fails, server fallback may queue the upload but should be monitored.

A finalize error means the app could not confirm the uploaded object and mark it ready. The object may or may not exist in storage. Use the workflow recovery controls to finalize, discard stale upload, or replace the source depending on the state shown.

• Open the workflow activity feed for the latest error message.
• Check whether the source file has the expected projection, metadata, or internal structure.
• Retry failed processing only after fixing the source issue or confirming the error was transient.
• Replace the source if the file is invalid or was uploaded to the wrong workflow.

• Missing pair: upload the missing RGB or thermal side, then refresh pairs.
• Conflict: inspect candidate items and assign or remove duplicates.
• Duplicate group: decide which media should remain active for review.
• Bad metadata: verify filename and capture-time patterns before rebuilding.

• If an image viewer fails, confirm the media item has a valid view URL and content type.
• If the orthophoto viewer fails, confirm the COG output is ready and has projection metadata.
• If the point cloud viewer fails, confirm Potree metadata and hierarchy files are available.
• If rendering is slow, reduce point budget, disable heavy overlays, or switch to a lighter product mode.