The resolver seems befuddled at times. Why?
Especially at very high levels, the resolver seems to take a longer time to find a resolve than one might expect. The reason is that it starts its resolve search looking only for “high quality” resolves, and throwing away huge numbers of “low quality” ones. It assumes that you would press F12 to throw away the low quality resolves anyway. So it is initially reluctant to show a lot of resolves. After it has shown all the high quality resolves it can, it lowers its standards and shows the ones that it skipped. Things that make a resolve high in quality are brevity, short promenade distance, and avoidance of such things as extend, slip the clutch, and reverse single file promenade. The promenade distance criterion is only applied at C2 and above.
