CLIENT141: Search results did not match
What this means
Search showed some results that don't match your products, so WCPOS hid them.
Nothing to do unless search still looks wrong — then reload WCPOS.
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. The app may also rebuild the index by itself, but only once per list per session, so a rebuild isn't guaranteed.
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
- Nothing to do unless search still looks wrong — sales can continue normally. If you want to check, 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 search still shows wrong results, or misses a product, customer or order you know exists, 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, use Copy debug info on the Logs tab and contact support — the entry's context names the list that was affected and the search that triggered it.