CA Service Desk Manager 14.1 / 17.1
The reason why this occurs is because rather than have all servers go to the database to get the next ID or next ticket number, they instead get a range of numbers and this reduces the number of times they need to go to the database.
For example, for IDs, each server asks for a range of 50. And for ticket numbers, the range is 2. These numbers are hard-coded.
Maybe they should be made configurable, so that is why I am suggesting an Idea so that it can be reviewed further.
This problem was not in 12.7 because in 12.7 all servers would go via one single bpvirtdb_srvr process but now in 12.9 and forward, each APP server has its own bpvirtdb_srvr process.
If they want to see the ID values and how it changes over time, they can look at the kc table.
This is an expected behavior as per the product design when working in AA