I see that my change of AP name was stuck as you describe and I could apply it again. But it was only the the name change that was presented as not applied. The changes on channel and signal was not display among pending changes and status and conf is unchanged. And if I only do the radio changes it will not be displayed as pending at all. Here below is my config history on that VC. It does not show any entry on radio parameter changes at all even if i have tried several time now. I probably need to open a support case on this. I have two separat systems but both same release on Airwave and APs. both system behave the same way 2017-06-28 14:27:22,095 INFO Config 4 Config Result Config Status: success Config Push Result: per-ap-settings 40:e3:d6:ce:8d:6c: OK hostname "TestAP_131": OK exit: OK 2017-06-28 14:26:36,980 INFO Config 4 Message sent { "command": "audit_result_update", "ap_id": 4, "audit_status": "Good" } 2017-06-28 14:26:36,980 INFO Config 4 cluster [SiteLab] has been updated, disabling auto-repair 2017-06-28 14:26:18,700 INFO Config 4 sending delta: { "ap_id": "4", "command": "config_update", "delta_config": "
per-ap-settings 40:e3:d6:ce:8d:6c
hostname TestAP_131
exit
", "hashed_management_password": "0" } 2017-06-28 14:26:12,670 INFO HTTP[1] 4 [] 2017-06-28 14:26:12,669 INFO HTTP[2] 4 Message sent { "ap_id": 4, "command": "request_audit" } 2017-06-28 12:57:49,192 INFO HTTP[1] 4 [] 2017-06-28 04:23:05,518 INFO Config 4 cluster [SiteLab] is not in auto-repair mode, skipping 2017-06-28 04:23:05,518 INFO Config 4 Message sent { "command": "audit_result_update", "ap_id": 4, "audit_status": "Good" } 2017-06-28 04:23:05,418 INFO Config 4 cluster [SiteLab] is not in auto-repair mode, skipping 2017-06-28 04:23:05,418 INFO Config 4 Message sent