Use each symptom to identify likely checks, then take the least destructive recommended action.
Check: the Application Log for path, permission, open, migration, or schema messages. Confirm another process is not locking the file and that the application-data location is writable.
Action: preserve the live database and logs. Do not delete or recreate the database. Use a verified compatible backup or the recovery guidance supplied by Database Status.
Check: that the selected dataset matches the importer and retains the provider's required header/order. Confirm prerequisite Parts or Minifigs catalogs were imported where required.
Action: obtain a fresh provider download and retry. Review the displayed validation error; a rejected import does not require deleting the existing catalog.
Check: whether the archive is corrupt, encrypted, ZIP64, oversized, lacks the expected CSV, or contains multiple ambiguous CSV candidates.
Action: use an intact normal Rebrickable download or select the direct CSV. Nested folders are supported; do not rearrange archive contents merely to make the importer guess.
Check: Parts Catalog content, spelling, and exact provider number. Part Reference contains a curated subset, not every catalog row.
Action: import/refresh Parts Catalog, search there, and send the exact row to Add Part.
Check: that Try BrickLink ID is enabled, Rebrickable settings are available when enrichment is needed, and the identifier is a Part identity rather than an item description.
Action: retry using the exact known Rebrickable Part number or review existing external identifiers in Part Details. BrickSuite does not invent a mapping when none is supported.
Check: network/provider status and the catalog image URL. A definitive Set or Minifig HTTP 404 is remembered for that exact URL; transient timeouts, DNS errors, cancellation, 429, and server failures remain retryable.
Action: correct provider configuration or wait before retrying a transient failure. A later catalog URL change permits a new request.
Check: the correct provider tab, saved credential, Test Connection status, Rebrickable session throttling, and Brickset daily threshold.
Action: correct the credential privately or use the supported CSV/ZIP fallback. Never paste API keys into logs or support reports.
Check: that BrickSuite Server is running, the wss:// hostname and port are correct, and the certificate fingerprint matches the Host. For a Protocol 1.3 paired device, also check whether the device is paired, revoked, waiting for re-pairing, or temporarily authentication-throttled. A Protocol 1.2 legacy client must have the Host's current shared access token. For Internet access, also check manual router forwarding and the Host firewall.
Action: compare the fingerprint directly with Host Server Settings and use Test Connection. Re-pair a device when required, update a deliberately rotated legacy token, or explicitly re-trust a regenerated Host identity. Never disable TLS verification. BrickSuite does not configure router or firewall rules.
Check: operation type, preview errors, Part/Color resolution, Storage capability, Manufacturer, Condition, Ownership, and projected quantities.
Action: resolve every blocking preview row before Apply. Use Compare Only for reconciliation without changing BrickSuite. Cancelling leaves inventory unchanged.
Check: that the location is active and a leaf. Inventory requires Inventory or Both; Collection requires Collection or Both.
Action: edit the location on Storage or choose another eligible leaf. Parent/container locations remain hierarchy nodes.
Check: exact required Part/Color, available quantities, other Build allocations, and physical record distinctions.
Action: add/receive inventory, release an inappropriate allocation, allocate a specific eligible lot manually, or use Missing Parts.
Check: both the original logical requirement and effective substitute Part/Color.
Action: edit or clear the explicit substitution. Do not expect similarly shaped parts to substitute automatically.
Check: that pulled quantity does not exceed allocation, CSV identity columns still match, and the Build/requirement has not changed since export.
Action: correct the previewed row or export a fresh Pull List. Apply only a clean reconciliation.
Check: active leaf status and Collection/Both capability.
Action: update Storage capability or leave the item Unassigned until a valid destination exists.
Check: whether it predates authoritative set_catalog_id storage.
Action: use Link to Sets Catalog... when offered and confirm the exact catalog Set. BrickSuite does not infer identity from the display reference.
Check: backup root, current status, retry eligibility, Application Log, and Database Status. Integrity damage, FK violations, and operational busy/open/query failures are different conditions.
Action: for an unavailable destination, restore access or choose a valid root. For an operational check failure, wait or close competing access and retry. For a confirmed health failure, preserve every existing file and follow recovery guidance; retention did not run.
Check: the complete Database Status result and diagnostic summary.
Action: stop unnecessary writes, preserve the live database/backups/log, and restore only a verified compatible backup. Do not assume making another copy repairs damage.
Check: the reported table, row, and parent information. This is a relational consistency problem and is distinct from an integrity-check failure.
Action: preserve evidence and follow Database Status recovery guidance rather than manually deleting rows.
Check: that the file is a readable BrickSuite SQLite database whose schema version exactly matches the running application.
Action: choose a verified same-schema backup. Older or otherwise mismatched schemas are rejected rather than silently forward-migrated during Restore.
Use Tools → Database Status & Integrity → Copy Diagnostic Summary for bounded database context and Help → Application Log... for operational messages. Sanitize personal paths and identifiers, and never share credentials.
Database Status & Integrity | Backup / Restore | Application Log | Help Home
For model or topology failures, start with 3D Printing and Prepare for Printing. External repair must still follow Local Printable Override validation. For direct Set part-out, review composition and Storage prerequisites; unresolved identities, uncertain nested composition, or a Remote connection can block the operation.