Gateways - List Gateways REST API return wrong OnPremises gateway version number

[PhilippeDuroche]

Hello,

When I check the version of my on-premises gateway in the Fabric administration portal, under the Connections section, I see the version number 3000.278.5. However, when I make a call to GET https://api.fabric.microsoft.com/v1/gateways using the documentation at https://learn.microsoft.com/en-us/rest/api/fabric/core/gateways/list-gateways?tabs=HTTP, I see the older version number 3000.266.4.

Is there a refresh delay? Could this be a bug?

Thank you.

[v-sgandrathi]

Hi @PhilippeDuroche,

As we have not received a response from you yet, I would like to confirm whether you have successfully resolved the issue or if you require further assistance.

Thank you.

[PhilippeDuroche]

@v-sgandrathi Hello. The problem is still there. Please don't close the tread yet.

Thank you.

[v-sgandrathi]

Hi @PhilippeDuroche,

Thank you for the update.
Noted, since Microsoft Support has already contacted the product group, we'll wait for their feedback. We'll keep the thread open until you confirm the issue is resolved on your end.

Let us know if you receive any additional updates from support.

Thank you.

[jwinchell40]

@PhilippeDuroche - We have had the same exact issue for a very long time.  We have a Notebook that inventories all of our gateways and reports back versions.  This job has been running for 6+ months and the Gateway version numbers never seem to update.

I would be interested to hear what support says about this.

[PhilippeDuroche]

@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?

[jwinchell40]

@PhilippeDuroche - 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.

[PhilippeDuroche]

@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.

[v-sgandrathi]

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.

[PhilippeDuroche]

Thank you for your answer, I appreciate it.

About the 24hrs period to wait for cache refresh, some of my version numbers in the API are as old a a month ago. Clearly something is not working as intended.

I opened a bug on the Fabric Portal.

[v-sgandrathi]

Hi @PhilippeDuroche,

Thank you for the update. Since you have raised a support ticket in the Fabric portal, a specific engineer from the Microsoft team will work with you to resolve the issue.

Thank you for being part of the Community Forum.