CLIENT141: Search results did not match
What this means
Local search returned results that do not match the catalogue; the app attempts an automatic search index rebuild.
To answer searches instantly, WCPOS keeps a local search index of the lists it searches — products, customers, orders and similar. A self-check found entries in that index that do not actually match what was typed. The mismatched results were hidden straight away, and the app attempts one automatic index rebuild per list per session to correct the index itself.
Your data
No store data was changed. This concerns only the local search index, which is derived from the data already on this device — hiding a mismatched result changes what search shows, never the underlying record.
Troubleshoot
- Usually no action is needed, and sales can continue normally — but re-run the search named in the log entry (its context records the search term) and confirm the results now match what was typed, with nothing you expected missing.
- If a product, customer or order you know exists is still missing from search results, reload the app — on web, reload the browser tab; on desktop and mobile, close and reopen the app. That lets it attempt a fresh index rebuild the next time the problem is detected.
- If the code returns after a reload, export debug info and contact support — the entry's context names the list that was affected and the search that triggered it.