I think logging capability is very essential for all network access, and that should be the same with ClientConfig files sync'ed by Publication Manager and Authoring Bridge.  However, according to both clients (i.e. Publication Manager and Authoring Bridge) and Tridion Docs servers don't have capability to extend logging level for ClientConfig sync.  Is that true?

That is actually a problem when I troubleshoot ClientConfig sync issue with RWS Support.  RWS hosts six production servers for us, and those are workload balanced.  With that condition, unnecessary ClientConfig file sync happens when the timestamp would mismatch than previous file sync.  Even worse, each of users seem to be experiencing the unnecessary file sync issue differently, possibly due to workload balancer.  So, even though redeployment of ClientConfig files by RWS Support improved the consistency across six production servers for some users, I am hearing from some other users, hey, still experiencing that issue.  Although RWS Support have ever tried to make the folder content consistent again and again, that won't be suppressed fully.  We can't identify which production server the issue is remaining.

I don't know what the challenge is with RWS to implement that logging capability.  But, if that logging capability wasn't possible for RWS, can RWS take different approach to identify required ClientConfig file sync?