An Azure service that provides global content delivery and acceleration.
Hello @Patrick Harris,
Thank you for reaching out on Microsoft Q&A forum.
We are aware of similar purge timeout issues that were observed earlier this year and were later mitigated on the platform side. Since then, the issue was resolved for affected users, and we haven’t seen widespread reports recently.
To help narrow this down, could you confirm a few details?
- Are you purging all content (
/*) or specific file paths? - Does the timeout occur consistently on this endpoint, or only intermittently?
- Have you tried purging a small set of paths to see if that succeeds?
- Is this happening across multiple CDN profiles/endpoints, or just one?
If a smaller purge works but a full purge fails, it could indicate that the operation is taking longer due to the volume of cached content. Once I have your answers, I can check internally and guide you further if the error still exists.
For reference, you may also find these documents helpful:
Please let me know your observations, and I’ll be happy to assist you further.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.