FIND finds record with unexpected sequence number

FIND returns a record with an unexpected Sequence Number in the field
FIND FIRST finds a Sequence Number one less than the value requested
There are times when the Sequence Number is wrong followed by periods when they are correct
Sometimes re-trying the transaction returns the correct Sequence Number in the field

Problem statement is similar to:

FIND FIRST Customer NO-LOCK WHERE Customer.CustNum = cMyCustNum NO-ERROR.


 

Sequence numbers are not approaching the maximum integer value

The application code and a database trigger are both using the same Sequence.

As a result of the particular logic used, not every consecutive number in the sequence is represented in the database (i. e. there are gaps in the sequence).
When a record with a "missing" sequence number was requested, the FIND statement failed. The application code did not account for this condition and processed the record that was already in the record buffer.

When values from the same Sequence are used at multiple points in the application, use caution when making assumptions about how sequence numbers are assigned to records. To handle gaps in the sequence, examine the properties of the ERROR-STATUS handle after the FIND statement in order to  identify cases when a record cannot be found.

For example: