AUTH131: Store session incomplete
What this means
The saved store session was incomplete, so WCPOS returned to the store list.
WCPOS remembers which site, cashier and store were open so the till can resume where it left off. This time part of that record was missing — usually the site or cashier entry — so instead of opening the store with a broken session, the till returned to the store list. Choose the store again to sign back in. Before this check existed, a till in this state showed a red "useStoreSession must be called within an active store session" banner over a blank window and could not get past it.
It usually means the device's local storage failed to keep something the app wrote. One occurrence is worth noting; a repeat on the same device is a storage problem to chase.
Your data
Only the pointer to the open session was cleared. The store's local data, including any sales still waiting to sync, stays on the device.
If the site or cashier is still in the list, choosing the same store again picks up that same local data. If the site had to be added again, the till opens a fresh local copy of the store: sales that were still waiting to sync under the previous session stay on the device but are not picked up automatically. If you know there were unsynced sales, contact support before clearing local data.
Troubleshoot
- Choose the site and store again to sign back in — the store's data on this device is untouched; only the remembered session was cleared.
- If the site is no longer in the list, enter its address again and sign in. Contact support first if you know sales were still waiting to sync — see "Your data" above.
- If it happens again on the same device, its local storage is not keeping what the app writes: check free disk space, and look at the Logs screen for storage errors from around the same time.
- Export debug info and contact support if it keeps recurring — the log entry names which part of the session was missing.