This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 26%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKU%3C/text%3E%3C/svg%3E)
Hi,
I have AD B2C custom ploicy release pipeline in Azure DevOps. Everythig was working fine but recentlty my pipeline is failing due to (504) Gateway Timeout.
The error I'm getting is below;
Invoke-RestMethod : The remote server returned an error: (504) Gateway Timeout.
At D:\a\1\s\custom-scripts\custom-policies-test-deployment-script.ps1:50 char:17
Same issue here... It is causing havoc on multiple clients' pipelines
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 75%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESV%3C/text%3E%3C/svg%3E)
FYI Seems it's working again.
Hi All,
I got confirmation from Microsoft this issue has been fixed and working now.
This should be fixed now for everyone! If anyone is still experiencing the error please let me know.
Best,
James
Thanks. It seems like fixed because I'm not facing any issue by running my pipeline.
Thanks @ JamesHamil-MSFT. It is working now.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 35%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hi folks,
I have also this issue, and I have implemented a retry mechanism and thanks to that, I am able to successfully deploy the policies via Azure DevOps. I hope that Microsoft will fix it soon, as the management API seems not be reliable right now for Azure AD B2C.
Hi Sriquen, Please could you share this retry mechanism please. Thanks
It is relatively simple. On my side, I have translated the script provided in the MS documentation into a C# console app, that take care of the errors returned by my httpclient, and retry the call for maximum 3 times. What I have seen then is that when deploying the first policy, it fails almost 100% of the time, but with this retry in place, the policy is successfully upload after 2 attempts. Then, all other policies are uploaded successfully after the first try.
It seems to me that the beta API for this endpoint is idle and needs to be waked up.
Are you still having the same issue? It looks like it's fixed for some users.
Thanks. It is seems like fixed and working.
Seems now that retry is not needed. Thank you for the follow up.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 7.000000000000001%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENW%3C/text%3E%3C/svg%3E)
We are also facing the same. Do we have any updates on a solution?