Forum Discussion
Power Automate Integration - ResourceNotFound
I logged a call with Microsoft and they said a mitigation has been deployed. I then went to my Chrome browser, cleared all browsing data (under advanced, left the passwords one unchecked) and can now edit my flow again from Power BI Service. The desktop tool is still an issue though...
Hi, tommmy
Based on the details you've provided, it seems like the "ResourceNotFound" error you're encountering might be related to the version of the Power Automate visual you're using. Since your colleague with version 1.1.17 of the Power Automate visual is not experiencing the issue, you can try the following steps:
1. You can try to update your Power Automate visual. Sometimes the new version of visual will fix related bugs.
2. You can create a new report and use Power Automate visual in this report to check whether it can be displayed normally to eliminate bugs in Power Automate visual.
3. Make sure that your Power Automate flow related parameters are set correctly and the requested resources exist. For the Power Automate troubleshooting process, you can click the link below and follow the steps in the document to troubleshoot.
Troubleshooting a cloud flow - Power Automate | Microsoft Learn
4. Make sure your version of Power BI Desktop is consistent with the version of Power BI Desktop of your colleague whose Power Automate is working properly.
If after updating the Power Automate visual the issue persists, could you provide more details about the specific steps you're taking when the error occurs? Additionally, knowing whether this issue is isolated to a specific report or if it's occurring across multiple reports would be helpful.
How to Get Your Question Answered Quickly
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for the response. I am running the latest version of PBI desktop so by default the Power Automate visual should also be up to date - downgrading to a release that contains the older 1.1.17 visual isn't an option. Regardless, this isn't just a desktop issue as the web experience generates the same error, suggesting the fault lies with the integration/current version of the power automate visual.