Possible issues with entry_id field

Hi,

We have observed channel entry_id field is always increment with 1. However, with a latest download for a device we have noticed that some data back from 2015/16 has following inconsitencies for entry_id values:

1. entry_id is not always increment of 1 from previous feed line.
2. entry_id are allocated in random order. e.g. Channel data starts with entry_id 4 and then few weeks later I notice rows got entry_ids as 1, 2, 3..... I am pasting some data below as a reference

Data download related to issue#1 {See line 2 and 3 have very large gap between two entry_ids.}

created_at,entry_id,field1,field2,field3,field4,field5,field6,field7,field8

1. 2015-11-28 23:06:50 UTC,21065,2578.26,702.47,79.84,5.00,1.00,1.00,,
2. 2015-11-28 23:07:10 UTC,21066,2652.53,737.65,69.88,3.12,0.47,0.47,,
3. 2015-11-28 23:07:30 UTC,52373,2721.32,732.05,77.89,5.89,0.00,0.00,,
4. 2015-11-28 23:07:50 UTC,52374,2729.25,748.50,93.55,3.80,0.00,0.00,,

Sample data related to issue#2 {See line 3, 4 and 5 entry_ids as 1, 2 and 3. Also lines 6 onwards entry_ids not in sequence. Massive gaps.}

created_at,entry_id,field1,field2,field3,field4,field5,field6,field7,field8

1. 2015-12-15 19:45:20 UTC,91133,750.57,204.90,19.19,1.00,0.10,0.10,,
2. 2015-12-15 19:45:40 UTC,91134,741.41,208.41,28.45,0.00,0.00,0.00,,
3. 2015-12-15 19:46:40 UTC,1,755.29,221.38,17.19,2.14,0.00,0.00,,
4. 2015-12-15 19:47:00 UTC,2,716.86,190.27,10.95,0.36,0.00,0.00,,
5. 2015-12-15 19:47:20 UTC,3,767.32,202.82,12.00,0.91,0.77,0.77,,
6. 2015-12-15 19:47:40 UTC,359,732.68,201.64,15.95,1.50,0.50,0.50,,
7. 2015-12-15 19:48:00 UTC,2142,664.57,184.62,14.05,1.10,0.00,0.00,,
8. 2015-12-15 19:48:20 UTC,3830,732.45,193.95,25.35,1.50,0.80,0.00,,
9. 2015-12-15 19:48:40 UTC,5529,829.42,227.84,24.95,1.26,0.53,0.00,,
10. 2015-12-15 19:49:00 UTC,7341,618.15,160.60,15.35,0.65,0.00,0.00,,

Highly appreciate your time to review this and comment!

Thanks

[Christopher Stapels]

The entry id is not a recommended way to retrieve data. Unfortunately, we aren’t able to guarantee the order of the entry id's in you feed data. We recommend reading by time or number of entries. We have made moves to remove it from the documented API's; entry_id may possibly be deprecated in the future.