Forum Discussion

Nytar's avatar
Nytar
Frequent Visitor
7 months ago
Solved

Semantic Model Refresh pipeline activity fails across multiple tenants (different errors)

Hi, Is anyone else having issues with the Semantic Model Refresh activity in Fabric pipelines?

I’m seeing it fail in multiple tenants with different errors (no tables listed, “workspace not found”, “Discover permission denied”), while manual refresh of the same semantic model works fine.

I’ve tried new models, new connections, republishing, service principal vs user, etc. None of it fixes the pipeline refresh.

Has anyone found a workaround other than avoiding this activity ?

Thanks!

 

 

 

data engineering
data pipeline
  • tayloramy's avatar
    tayloramy
    7 months ago

    Hi Nytar, 

     

    I've seen so many issues with this activity. in my opinion it should be pulled back into preview and fixed. 

    I only ever use notebooks and the APIs/XMLA endpoints to refresh my models. Much more reliable. 

     

    I do recommend creating a support ticket to microsoft, the more people that create support tickets about this activity the more likely it is to be priortized to be fixed. 

     

     

2 Replies

  • tayloramy's avatar
    tayloramy
    Super User
    7 months ago

    Hi Nytar, 

     

    I've seen so many issues with this activity. in my opinion it should be pulled back into preview and fixed. 

    I only ever use notebooks and the APIs/XMLA endpoints to refresh my models. Much more reliable. 

     

    I do recommend creating a support ticket to microsoft, the more people that create support tickets about this activity the more likely it is to be priortized to be fixed. 

     

     

  • v-veshwara-msft's avatar
    v-veshwara-msft
    Community Support
    7 months ago

    Hi Nytar ,

    Thanks for reaching out to Microsoft Fabric Community.

    Just checking in to see if the suggestions and alternative approaches shared by tayloramy  were helpful.

    If the pipeline activity continues to fail, using the alternatives mentioned earlier may be the best option for now.

     

    Additionally, could you please confirm whether the issue has been addressed through the support ticket with Microsoft?

    If the issue is now resolved, we’d greatly appreciate it if you could share any key insights or the resolution here for the benefit of the wider community.

     

    Thank you.