0050362: Add a check to automatically restart a cashup if current one is already processed

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0050362

Retail Modules

Web POS

public

2022-09-27 23:49

2022-09-28 23:37

Reporter

AugustoMauch

Assigned To

AugustoMauch

Priority

normal

Severity

major

Reproducibility

random

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

RR22Q3.1

Fixed in Version

RR22Q3.1

Merge Request Status

Review Assigned To

OBNetwork customer

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0050362: Add a check to automatically restart a cashup if current one is already processed

Description

We have detected that sometimes there is a problem with the state persistence and as a result after completing a cashup, the cashup that was just completed remains in the status of the application. Then, the next time the cashier logs in he will keep using that cashup, and he will end up with an error in the backend after trying to process a cashup that has already been processed.

We are still trying to find the root cause (state not being persisted properly), but in this issue we mean to prevent the duplicated cashup processing by checking if the user is working with a processed cashup and creating and in that case creating a new one

Steps To Reproduce

We are not able to reproduce the issue unless we:
- Increase the throttle of the state persistence from 100ms to 10s
- Remove the state persistence flush we do after each cashup completion

Doing that, if the user closes or refreshes the application right after completing the cashup, the completion will not be persisted and the next time the user logs in he will keep using the previous version of the cashup

Proposed Solution

Additional Information