When loading the SAZ file, the requests are ordered incrementally based on the order they were saved in.
For example, a Fiddler session was sorted by URL and then saved to SAZ. When the file is loaded, the requests are still sorted by URL but the original index numbers are lost and the requests are numbered incrementally as per this sort. This means that it is not possible to sort the session back to the original linear order by clicking on the index column (#) as it was possible to do before the save/load.
I've seen that the original index is saved in the Comments column. This is only a partial solution because:
1. When sorting by this column, a lexical sort is performed meaning the sessions would be numbered: 1,10,100,101,11,12..19,2,20,21 etc...
2. If the request had a comment associated with it, this overrides this feature and the original index number is lost.
Also, I know it's possible to sort by ClientDoneRequest as a good approximation but it obviously doesn't recreate the original order.
It would be beneficial to keep the original index numbers (even including the gaps between them) as there is information there that shouldn't be lost when saving.
As always thank you for your work on this wonderful product.