That's a plausible explanation.

If Microsoft solves the issue within the next 30 days, I will consider that you were right.

"30 days" is an arbitrary extension of the timeline for something that was reported 4 months ago to Microsoft, and should have been already fixed.