Sequencing issue in ID in CMN_AUdit Table

Products

• Clarity PPM SaaS

Issue/Introduction

We are observing an issue in the ID sequencing in CMN_Audit table.

The latest created record doesn't have the maximum ID.

For example, the record created at 2023-03-02 23:58:37.067 timestamp has 16715517, however the record created at 2023-03-02 23:59:10.42 which is the latest one has 16715502.

Ideally ID of record created at 2023-03-02 23:59:10.42 should be greater than 2023-03-02 23:58:37.067 but in this case it viceversa.

We would like to understand what the expected behavior in this case.

We have an critical outbound interface written on the max logic, and I am afraid we might have recode the interface as this behavior is not consistent. Looking forward to hearfrom you.

Environment

Release : 16.1.1

Resolution

Clarity app servers caches IDs in 1000s increments and depending on which node a given user is at you could very well see this type of scenario and it is not an issue. It is not gauranteed that these IDs will always be in order but what is gauranteed is that they should be unique.