When creating multiple records in quick succession via the API, process numbers could be determined incorrectly

When creating multiple records in quick succession via the API, instances could occur where a process number was determined incorrectly. This could result in a number being used that was already present in the system, causing the record creation to fail. Process numbers are now correctly reserved, ensuring that unique numbers are used even with rapidly consecutive API calls.