15/7/2026

Bug-Fixes

#1 Eliminated API race conditions for duplicate invoice submissions, ensuring data integrity and improving overall queue stability.

1. Overview

Resolved an API race condition issue where simultaneous, duplicate invoice submissions resulted in mismatched UUIDs between the client's API response and the JomE database.

2. What Has Changed

Previous:

When a client submitted the identical invoice payload multiple times at the exact same moment, a race condition occurred in the background queue.
This caused the system to occasionally process the secondary submission before the primary one.
Because a new, unique UUID was generated for each API request, the UUID returned to the client's system did not match the final UUID stored in the JomE database for that invoice.

Now:

The system now incorporates strict sorting by submission ID if the creation timestamps are identical.
If an invoice number is already actively being dispatched by the system, any subsequent duplicate submissions are intentionally delayed in the queue.
This prevents simultaneous processing, effectively eliminating the race condition.

3. Impact

Data Integrity: Ensures that the JomE UUID returned to the client via API perfectly matches the UUID stored in the database for the exact same invoice.
Queue Stability: Prevents concurrent processing collisions when high-volume users accidentally send duplicate payloads simultaneously.
Reliability: Improves overall API synchronization and prevents downstream reconciliation issues for clients.