Facing (ir_sequence_strict) Error at Front Desk Office after clicking on PAY NOW Button

Support Developer
1

We are using Tryton 6.0/GNU Health 4.2.0 development & Our system is Facing this (ir_sequence_strict) Error again and again (many times a day) at Front Desk Office after clicking on PAY NOW Button. When ever a sale is made, at Pay Now button pressed cause this error (ir_sequence_strict) on Every FDO Desk at same time.

After closing this error and performing same action, this error disappears and Pay Now successfully Done.

Now we are unable to track this from where it has been raised and what are the causes for this Error.
Error snaps are also attached. :pensive_face:

image
image1368×773 134 KB

image
image1282×862 216 KB

image
image982×741 159 KB

2

This is a constraint in place to avoid missing invoice numbers. So if many users are doing this multiple times a day, it can happen when one of them triggers the action while another one is waiting for it to complete.

This should be very rare, unless you have a lot of users, or if the action itself is very slow.

More recent versions try to be more intelligent on this and will retry a few times in the background, leading to some waiting for the occasional unlucky user, but no errors.

3

It will be interesting to have the full traceback in plain text to understand exactly where this happens.

But you can still start by increasing [database] retry.

If it is not enough, it will be necessary to analyze and see if it is not possible to use different sequences to reduce the contention.

By the way, series 6.0 is no more supported, you should consider upgrade.