Hello Uday

This might be caused because of how the sequence works

when you run next_by_id odoo gets the next sequence and increase the current one so if you call it and didnt use it you will find gaps

you could try the following to reproduce issue:

1- create a new record and then click discard and see if the sequence changed

2- upload data using excel and click on test after that check the sequence you will see that it increased

you can solve this by changing the place you call the function instead of running it in the create function or on_change run it in the confirm or something like that

Hello Uday,

Yes, this behavior is very likely due to a race condition caused by the custom _compute_name override using next_by_id() during concurrent invoice posting.

To reproduce this locally, you can:

• Simulate multiple users posting invoices at the same time (e.g., using multi-threaded scripts or tools like JMeter/Postman runners)
• Run Odoo with multiple workers enabled (not in single-threaded dev mode)
• Trigger simultaneous invoice creation/posting to force concurrency

However, it's important to note that Odoo’s standard sequence mechanism already handles concurrency safely. Overriding _compute_name and calling next_by_id() directly can bypass those safeguards, leading to gaps.

A better approach would be to rely on Odoo’s built-in sequence handling during action_post() or ensure proper locking if customization is required.

Hope this works for you! If you need any help implementing this or want a more optimized approach, feel free to reach out for further discussion.

Regards,

Zehntech Technologies Inc.

santosh.sekwadia@zehntech.com