The connected Power BI Semantic model is no longer found --- Dynamic subscription

[Ingo_BI]

Hi,

I try do create a dynamic subscription but get this error message. 

I have tried to re-publish the desktop file to Service but it does not solve it.

What might be wrong?

[Lomannn]

Hi,

I have had this issue since last week. Does anyone have a solution?

[ripleym78]

Hi, I'm no tsure if this is a solution or not, but a combination of republishing semantic models and reports and recreating subscriptions seems to have got things working for us again.

[Lomannn]

Hi,

Thanks for your response. I tried that already. Initially, it was connected to Dataflows, but I switched to direct SQL Server connection (import mode), which didn’t solve the issue. I even deleted everything and rebuilt it, but there was no effect.

Do you have any other suggestions?

The account has Power BI Pro, and the workspace is on Premium capacity. It worked fine for a few months, but since last week, it hasn’t been functioning.

[ripleym78]

Hi, we have just started running into this issue as of Monday this week.  Subscriptions were running fine before then, and some continue to run, however the dynamic ones are coming up with the error message: The connected Power BI Semantic model is no longer found. It may have been deleted or renamed.

[Jon-Meakin]

I just rebuilt the subscription. Ironically from the same dataset that the existing subscription claimed was no longer available (and the subscription itself continued to function; I just couldn't edit it).

I know the Power BI Service effectively duplicates workspaces for apps, so in some contexts you can see duplicates of reports. Workspace version vs app version, etc. I wonder if it's doing something similar here -and the copy it relies on has vanished- but I can't think why it would need to. Especially as the subscription keeps working anyway.

[ripleym78]

Our dynamic subscriptions aren't working.  Standard subscriptions are, but for the ones where want to filter and send out to a dynamic recipient list based on content, that's where we're getting the error message.

And the subscriptions aren't even firing, by the look of things.  I.e. when I update it to only send to my email I don't get anything.

[Jon-Meakin]

Not even on a test? That seems odd. 

Is it a big job to rebuild? Although mine was working, I did need to change it so just gave up and rebuilt. Not seen the error since.

[SebFuze]

Hi, I have the same issue and I tried to rebuild my subscription but I still have the error. 
Did you change something when you rebuilded your subscription ? 
Thanks 

[Jon-Meakin]

No, not at all. It's a fairly fundamental but basic error, so I'm not sure there is much you can do different.

The same dataset was always being used for various subscriptions, all of which were running fine (as I've said before, even the one with the error). 😞

Because we use flows a lot, the dataset was spun up just for subscriptions, so it's very small. Is that an option? Create a new dataset with the minimal requirements?

[ripleym78]

Yeah, same as SebFuze, a couple of us have tried to edit and save, or completely rebuild the subscription, but still not working.

Our alternative at this stage is Power Automate, but that seems unnecessarily complicated when we have subscriptions which should work.

[tomtsa]

Hi!

Just ran into this error myself. Have you been able to get it working or work around the issue?

I have just created a test dataset to my own workspace, so I must have access to this dataset. Still I keep running into the same error.

[Jon-Meakin]

I'm curious about this too. 

We're seeing a unprecedented increase in capacity usage at the time our subscriptions are being sent. I reviewed the subscription settings to make sure there was nothing silly and saw this error:

The model is absolutely still there and is working fine independently of this process, but in the context of this existing dynamic subscription, is now greyed out. It sits in a workspace with other datasets with the same levels of permissions. If I step through this  subscription to reconfirm previous settings, the query builder works but it won't 'Save & Close'. I assume because of this error. 

And yet the subscription continues to work, albeit generating excessive overheads in capacity availability.

If I start a brand new subscription, I can select the same dataset, build the query and save it.

[collinq]

Hey @Ingo_BI ,

The message states that the data source is not there. Do you know that it is there for sure?  Do you know that your userid has permissions? And, is it possible that it was renamed?  Does this work without the subscription?

[Ingo_BI]

To my knowledge it is there. The report works just fine in Service and the semantic model is there aswell. It exists in my own Fabric Trial workspace so I should have the right permissions.

[collinq]

Hi @Ingo_BI  and @Jon-Meakin ,

I think that since you are both experiencing this and you both are sure that the error message is sending you an error that you should open a ticket with Microsoft.  And, please post here the results for all of us.

[Jon-Meakin]

Thank you, @collinq. I've made some changes to see if the capacity usage drops this evening. I will raise this tomorrow if the error hasn't resolved.

[Cosmic_Panda]

Hey,
Any update on this? Did you manage to get it resolved?

I'm having the same issue.

Thanks