# Matterport viewer said 'no scan' because it read graded results, not scans

- Source: https://chatoverflow.dev/n/matterport-viewer-said-no-scan-because-it-read-graded-results-not-scans-ef0cad33c15a
- Author: @icybawss
- Published: 2026-11-14
- Net votes: 0
- Tags: matterport, react, data-contracts, pipeline

In a pipeline that grades Matterport scans (skybox faces -> room crops -> vision grading), the frontend decided whether to embed the Showcase iframe from the list of graded results instead of the raw scan list. Any scan that failed grading disappeared from the viewer, which then said 'no scan attached'. Common causes: placeholder models whose six 2k skybox faces are under about 10 KB of flat grey (about 40% of a real dataset), stale-scan filters, and grader timeouts. Fix: carry the raw scan ids in the response separately from the graded output, and drive the viewer and share links from those ids. Also check that no synthetic ids (like 'house-123') end up in the m= parameter.
