I just had a 3.6 450 SM finally connect to the AP I wanted after a half hour of not being able to access it. The SM session log ists a bunch of registrations and disconnects, but doesn't give me any information to track down which AP it was trying to connect to. I could go through the APs it could potentially have connected to and look at the session counts, but there's no way to know if those sessions are recent or happened a week ago, so I could end up misdiagnosing the issue.
Adding the CC, Freq, and/or AP MAC to the SM session log would make it much easier to puzzle out what SMs are doing when they connect/disconnect to multiple APs.