Running PI 2.2.3, WLC 8.0.120
We have recently started finding that when we add a new AP it registers correctly with a controller but does not appear in Prime, or appears as a client! Workaround of running a sync on the controller in Prime resolves the issue and the AP then appears correctly in Prime and can be configured as normal. Not specific to any particular model of AP - we have a mix of supported models. Am guessing that a PI background task isn't functioning properly but not sure which or which logs I should be looking at to try and find the culprit. Any pointers or assistance would be greatly appreciated.