is it correct that the syslog triggered config collection only looks for changes in the running-config and the vlan config and NOT the startup-config ?
If this is truth this is the reason for false positives in OutofSync Report in RME > Config Mgmt > Archive Management
at least, if the process that checks if the running-config has changed recognizes a change and triggers the archive update of the running-config this could also trigger the archive update of the startup-config without the control of its need. But thus could prevent the false positives.
the amount of perhaps unnecessary network traffic because of unchanged startup-configs could be disregarded to the amount of work false positives can produce...
What version of RME? RME 4.0.6 and 4.1.1 attempt to fetch both running and startup configs on reception of a syslog config change message. Polling is done before fetching to prevent unnecessary traffic.