Common troubleshooting
Practical recovery paths when search, scanning, printing, saving, or permissions do not behave as expected.
Help updated for v0.10.21 · 2026-07-13
When search or scan does not find a record
Start by checking what kind of identifier you entered. Asset IDs identify serialized items, Type IDs identify inventory types, serial numbers may or may not exist on an item, and QR payloads may contain a URL or structured value rather than the visible code printed on a label. If the scan is valid but unknown, the app should offer recovery paths such as adding a missing type or item.
If search feels stale after editing a record, refresh the list or clear only the current filter before assuming the record was lost. The goal is for Pluck to preserve search context after edits, but older screens may still reload data more aggressively than they should. When that happens, use the debug widget or bug report flow so the team can see the route, action, and latest error.
When printing looks wrong
For normal documents such as reports, estimates, picklists, and assignment sheets, Pluck owns a safe page inset so content does not touch the physical edge of the paper. For labels, the app must preserve the sheet definition exactly. If labels drift, check browser scaling, page size, orientation, and whether the selected sheet matches the physical stock. Do not fix label drift by adding route-local margins; that breaks the physical planner.
If a print preview opens before images or fonts are visible, close the browser print dialog and use the preview Print button after the page finishes rendering. Label routes should wait for QR codes, barcodes, images, and custom fonts before opening print. Browser print dialogs can offer system dialog access, but Pluck can only call the browser print API directly.
When a feature is missing or locked
Missing controls usually come from one of three places: the company feature setting, the subscription or entitlement, or the user’s role permissions. Check those in that order before treating the page as broken. Some features are hidden when they do not apply; others are visible but disabled so the user understands that an upgrade or permission change is needed.
If a save fails, copy the debug details before dismissing the error. A good report includes what you tried to do, what you expected, what happened, and whether the issue happened after a specific edit such as changing an image, uploading a font, printing a label, or moving an item. That context is often the difference between a quick fix and a long guessing session.