https://devzone.nordicsemi.com/f/nordic-q-a/24370/fds-iterating-through-found-recordsIn the documentation it says the order in which the records are returned is undefined. However in my observations FDS always appears to work upwards in terms of record_id so older records are returned first. Can I ask when is it the case that it is noten-USTelligent Community 13Wed, 16 Aug 2017 12:40:04 GMThttps://devzone.nordicsemi.com/thread/95947?ContentTypeID=1Wed, 16 Aug 2017 12:40:04 GMT137ad170-7792-4731-bb38-c0d22fbe4515:82ae075f-0b58-40ed-9ce4-21b56b8b7875RichieJH<p>Understood, thanks.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/95946?ContentTypeID=1Wed, 16 Aug 2017 11:01:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:728c6c7f-15b3-4253-b52b-66ca2bf8705bemdi<p>There are several things to consider, for instance:</p> <ol start="2"> <li>how many pages you are using</li> <li>how many times you have run GC</li> <li>the length of the records</li> </ol> <p>Internally, fds maps <em>physical</em> pages to so called <em>virtual</em> pages. The <em>physical</em> page to which a <em>virtual</em> page is mapped changes after GC. Because fds looks through pages using their <em>virtual</em> index, the order with which records are iterated does not change.</p> <p>It might happen though, that when one page is almost full (e.g. page A) and you attempt to write a new record, it will get written to another virtual page which has enough space instead (e.g. page B). If a smaller record is written afterwards, it will be written to page A if it fits.</p> <p>Then you&#39;d have a situation where you&#39;d iterate a more recent record before an older one. But once that order is estabilished, it does not change.</p> <p>emdi</p><div style="clear:both;"></div>