Concurrent manager question - urgent

I need answer to the posed question ASAP. This is new implementation of 11.5.10.2 PRODUCTION and business users are nervous about this.

Problem Description: We are now live with 11.5.10.2 today, first day. we have noticed that holes are appearing in the sequencing of the concurrent request Ids. For example, the fnd_concurtrent_requests table contains these records:

SQL> select request_id, request_date, phase_code, status_code
from fnd_concurrent_requests
where request_id >= 1726872
and request_id <= 1730794
order by request_id;
REQUEST_ID REQUEST_D P S
---------- --------- - -
1726872 15-FEB-11 C C
1726873 15-FEB-11 C C
1726874 15-FEB-11 C C
1726875 15-FEB-11 C C