Time marks not present in post-processed coordinates

According to the docs either GAL or GLO is recommended for time marks logging:

https://docs.emlid.com/reach/common/reachview/rtk-settings/#gnss-selection-for-time-marks-logging

Is this information outdated?

I get the feeling that my GLO data has lower quality compared to the GPS data (SNR, cycle slips). I also have data sets where I only can get a solution when skipping the GLO data. I thought that a higher data rate might provide more information and thus help to get a fix quicker/more reliable?

@mstrom you can check for valid and non-valid time marks in the OBS file with this tool: Timemark time machine: a script to manipulate events within RINEX 3.xx files