Report Not Found Error

[powerbiuserasu]

Hello. Recently I published a new report to an app and users are recieving a 'Report Not Found' error when going to the link. If you look at the navigation pane while the error is still up you can see the report name in the background and if you click out of the error message you can get to the report. Once this has happened and they go to the link a second time there is no error. At first we thought it was because the semantic model was in a different workspace but after fixing that we are still facing this issue. 

[v-aatheeque]

Hi @powerbiuserasu 

We wanted to follow up to check if you’ve had an opportunity to review the previous responses shared by @GilbertQ @tayloramy 
If you require further assistance, please don’t hesitate to let us know.

[v-aatheeque]

Hi @powerbiuserasu 

We’d like to confirm whether your query has been addressed. If you still need help, please let us know and we’ll provide further guidance.

[v-aatheeque]

Hi @powerbiuserasu 
Have you had a chance to look at the earlier response? Let us know if anything is unclear, and we’ll provide further clarification

[GilbertQ]

Hi @powerbiuserasu 

Please remember that what can happen sometimes is when you update the app, it does say it can take 10 to 15 minutes for the changes to be reflected. So if you can just wait and see if that actually happens

[tayloramy · Accepted solution]

Hi @powerbiuserasu, 

“Report not found” in an App typically means the URL you shared points to a report ID or page that isn’t part of the user’s current published app version (yet), or the user’s initial app install/permissions haven’t caught up. It’s common right after replacing a report, renaming pages (deep links), or moving from a cross-workspace model. 

Can you verify permissions and deep links and republish the app? 

Another thing that might help is having your users clear their cache in their browser. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.