Going sideways;
Thirty years ago, forcing the speed/duplex was a semi-common issue. But that problem no longer exists today. You have a deeper underlying issue if you are having negotiation issues, and at best, forcing the speed/duplex might mask it. Or worse still, hide the problem.
Before forcing the configuration, did the switch port and AP report that they had negotiated the same speed/duplex (such as 1Gb/s, 2.5Gb/s, etc)?
If so, were you getting anything reported like CRC errors, to give any indication there was a link issue?
If so, forcing the speed/duplex will have no impact on the issue. The issue is far more likely to like on the RF side, or with client drivers.
One of the most common issues I encounter with companies that have multiple APs is that they have not configured an RF profile. They left all the RF settings on their default settings. If you are not using a profile, try configuring one first and wait 24 hours to verify whether the issue persists or changes.
https://documentation.meraki.com/MR/Radio_Settings/RF_Profiles
While you are there, make sure you have enabled AI channel planning.

Also, check out Wireless Health and Overview to see if it is identifying any issues.
https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Meraki_Health_Overvie...

Having 2.4Ghz enabled is also a VERY common issue for performance problems. Try disabling it so that only 5Ghz is enabled.
The Learning Hub also includes an advanced training course (free) for WiFi. Modules 1, 2 and 3 are all about troubleshooting WiFi issues.
https://community.meraki.com/t5/Wireless-Advanced-Operations/ct-p/mroperations