Yes, currently there is neither a workaround nor a solution (at least I’m aware of). Further troubleshooting revealed that these clients are sending 15-20 Autodiscover requests per second! First I thought Exchange is causing issues as sending something wrong to clients, but all responses were good. I parsed the logs of all Exchange servers only for a few hours (we have hourly rotation configured) and I was surprised when I imported the CSV file:Įven though I parsed only a couple of hours, I got for the top User-Agent over 100 million hits!Īs you can see, obviously Apple based User-Agents are by far the ones, which sends the most requests to Exchange (look at the ridiculously high numbers!). I used the parameter -ClientReport, which collects the statistics about the User-Agents, their number of hits and the requested URI. I used my script Get-IISStats and parsed the IIS logs. Further investigation showed that the application pool for Autodiscover was constantly using 10-15% CPU and sometimes spiked for a few seconds up to 50%. SymptomĪll server showed an unusual high CPU usage. With high CPU usage I’m talking about 10-15% total usage across ALL servers and this constantly. It all started with seeing high CPU usage of the Autodiscover application pools on my on-premises servers. There could be other reasons but mostly things should work and get synced automatically as described above.Recently I stumbled across this issue, which was not obvious at the beginning. Also it won't run if the app is force quitted. It'll not run if battery conditions are not good. This will run as frequently as once per 10 minute to just once per day. On iOS, the conditions are 'Background App Refresh' turned on and 'iCloud Active sync' for faster initiating.īackground App Refresh is handled by iOS so it can't be tightly managed. Mac version should do it by itself if it's opened. If devices are connected and have iCloud (and iCloud Drive) turned on, it'll try to sync under the hood. If the underlying data is synced, GoodTask needs to fetch that afterwards.

This can sometimes happen on Mac and rarely on iOS. Sometimes this gets stuck and opening Reminders app reinitiates the process.

If something goes wrong here, there is nothing that GoodTask can do. Underlying data sync for Reminders database is done by iOS and macOS.

The logic behind sync is not that complicated.

Activesync mac