1. Mailing Lists
  2. Contributors
  3. Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

Avatar

Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

by
Ecosoft Co. Ltd., Kitti Upariphutthiphong
- 04/03/2024 16:59:56
Thanks everyone!

Reservation Method = Manual, sounds like a valid solution. We will test and report the result. 

On Mon, Mar 4, 2024 at 9:32 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:
If talking about picking generation, I wouldn't do reserve at that time, and do a general "reserve round" at the end of the batch, and thus, you remove the quant lock constraint.

Regards.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Reference