Forum Discussion
Gateways - List Gateways REST API return wrong OnPremises gateway version number
Hi PhilippeDuroche,
Thank you for sharing your observation, it's valid and appreciated.
The behavior you're seeing is a known issue caused by a metadata synchronization delay between the Fabric Admin Portal and the Fabric REST API. After a gateway update, the Admin Portal usually shows the latest version right away, but the REST API (specifically the GET /v1/gateways endpoint) might still display an older version due to backend caching or delays.This is typically temporary, and the API should update to the correct version within a few hours.
If the difference lasts more than 24 hours, it could indicate a deeper sync or caching issue. In that case, please submit a support ticket through the Microsoft Support Portal so the team can investigate. Also, make sure the API request is using the right tenant and gateway ID, especially if you have multiple gateways or clusters in your environment.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thank you.
jwinchell40 Hi! I spoke with microsoft support engineer and he told me he did some tests on his side and after updating his gateway, the api version was showing the right version number. He told me he was going to investigate my problem.
One thing that popped along our discussion is the fact that I'm using the DataGateway PowerShell module to update silently and automatically my gateways.
Are you updating your gateways with the pbigw (exe) installer or are you using powershell or some other scripting tool to automate the process of updating your gateways?
Resolver IIIPhilippeDuroche - We host a SaaS solution for customers so they are all running the On-Prem Gateway. When we request that they upgrade the version, they are doing through the normal UI installer. We just sent out an email Monday asking Clients to upgraded to version .278 and we have been watching whether the Gateway versions have been updating via the API.
I just ran the CLI command to get the Gateway version that way to see if it is any different. It is, but not in a good way. One of our clients who upgraded to .278 this week, the CLI comes back with a version of .200.
jwinchell40 Microsoft support confirmed something is wrong with service updating backend. They've put up a ticket to involve the product group. Will keep you posted.