Lakehouse schema change not updated in GraphQL API

Hi Mauro89 ,

We’ve seen the same thing in our workspaces, and right now GraphQL APIs in Fabric don’t automatically pick up schema changes from Lakehouse tables. Even if the table structure changes or new columns appear, the GraphQL item keeps using the schema it captured at the time the API was created. Because of that, the API won’t show new fields or updated types until you refresh it manually.

In our case, the only way to get the new schema to show up was to open the GraphQL API item, let it reload the metadata, and then save it again. Sometimes we even had to remove the table from the API and add it back. Once we did that, both the structure and the updated data started showing correctly.

So yes, this is a limitation at the moment — schema updates in the Lakehouse don’t sync automatically into GraphQL. Hopefully this becomes more dynamic in future updates, but for now, a manual refresh inside the GraphQL item is needed whenever the underlying table schema changes.

If you want, I can outline the exact steps we followed to force the refresh.

– Gopi Krishna