CLIENT142: Search index did not answer
What this means
The search index did not answer in time, so WCPOS searched the catalogue directly instead.
The local search index was still building or could not answer. On web this is typically because the POS tab has been in the background, or because another tab holds the database lead; on desktop and mobile it typically happens right after a large sync, or in the moments after an app restart while the saved index is loading back in. Searches still answer, from a direct scan of the data on this device, and switch back to the index automatically once it responds.
Your data
No store data was changed, and your search was still answered — a direct scan of this device's data answered it instead of the index. Searches may simply answer a little slower until the index takes over again.
Troubleshoot
- Usually no action is needed: search results keep working, and the index takes over again on its own once it responds.
- On web, if WCPOS is open in more than one browser tab, close the extra tabs — only one tab can lead the local database — and keep the POS in its own window rather than a background tab.
- If searches stay slow or this code keeps appearing, reload the app once — on web, reload the browser tab; on desktop and mobile, close and reopen the app.
- If the code still returns after that, export debug info and contact support.