Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi all,
I have thirty scheduled flows that sends emails when the Power Bi alerts are triggered.
The majority of this flows are working properly, but there are some of these that are failing without any explanation. (These alerts are the same to all the flows, but the filters change).
F.E. If we sell something in America, we send an email to the America's managers.
The error message that appears to me is the next:
IMPUTS:
I've been searching in the forum for a related or similar issue, but the unique solution proposed is to call Microsoft Technical Support, and for that I need a premium account.
I also have the same problem, I hope Microsoft will fix it.
Hi all,
I also have this same problem, does anyone have any idea what we can do?
Tanks for help me..
Best Regards..
@sannicolasalex wrote:Hi all,
I have thirty scheduled flows that sends emails when the Power Bi alerts are triggered.
The majority of this flows are working properly, but there are some of these that are failing without any explanation. (These alerts are the same to all the flows, but the filters change).
F.E. If we sell something in America, we send an email to the America's managers.
The error message that appears to me is the next:
IMPUTS:
{"host": {"apiId": "subscriptions/ac07fa44-4742-482d-aa28-c00945932935/providers/Microsoft.Web/locations/westus/runtimes/msmanaged-na/apis/powerbi","connectionReferenceName": "shared_powerbi","operationId": "CheckAlertStatus"},"parameters": {"alertId": "27914_"}}OUTPUTS:{"statusCode": 401,"headers": {"Pragma": "no-cache","Retry-After": "600","Strict-Transport-Security": "max-age=31536000; includeSubDomains","X-Frame-Options": "deny","X-Content-Type-Options": "nosniff","RequestId": "4aa9526c-8416-4dd1-afc8-44a7656acc0d","Access-Control-Expose-Headers": "RequestId","Timing-Allow-Origin": "*","x-ms-apihub-cached-response": "false","Cache-Control": "no-store, must-revalidate, no-cache","Date": "Thu, 26 Sep 2019 09:53:30 GMT","Content-Length": "220","Content-Type": "application/json"},"body": {"error": {"code": "PowerBINotAuthorizedException","pbi.error": {"code": "PowerBINotAuthorizedException","parameters": {},"details": [],"exceptionCulprit": 1}}}}
I've been searching in the forum for a related or similar issue, but the unique solution proposed is to call Microsoft Technical Support, and for that I need a premium account.
It seems that by the moment, there isn't a defined solution.
This is happening to my coworkers too.
I'm having a similar issue. All existing flows using Power BI alerts are working fine. But I cannot create new ones. They just say "Unauthorized"
The full text of the body of the error message is:
{ "error": { "code": "PowerBINotAuthorizedException", "pbi.error": { "code": "PowerBINotAuthorizedException", "parameters": {}, "details": [], "exceptionCulprit": 1 } } }
My Power BI connectors in Flow are ok. All existing flows using the Power BI connectors work fine. I just cannot create new flows.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingFWIW, I've opened a ticket. I'm having trouble with creating any new flows based on Power BI alerts as the trigger. I just tried to set up a 2nd flow based on an alert that I had set up over a month ago. The Flow created a month ago works fine. The new flow based on the same alert gives an unauthorized error.
Hoping support can assist in getting to the bottom of this.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingThanks, please if you find some solution keep the topic updated. I'm still having problems and the issue hasn't been solved.
Let's see if some technical role, can asists us. The most funny think, is that I have like 15 flows managing 15 alerts with the same code and the same development, that works properly in the same Power Bi and the same page. So I can't understand what are happening.
Thanks to all.
Hi all,
We managed to copy an old alert and change it to the new rule, this way it works, you can test?
Best Regards..
That did not work for me. It seemed to create ok, but once the trigger happend, it came back with the same Unauthorized error.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingGood news. I am told this is a known issue and is being actively researched and has an expected Oct 28, 2019 resolution, so put that on your calender. I will do mine on the 28th/29th as well and follow up with support on success/failure.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingHi all..
Do we have any updates on the fix that would be applied yesterday?
Tanks for help me..
Best regards..
Still not working for me, but it is a different error. No longer a "Fix the Trigger" error. I've sent the new error to MS. Progress, but not a fix, not for me at least.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingHi Ed,
At this moment I made a test creating a new one, without copying a previous one and I didn't have the error anymore, I think they are still changing the environment, if I can test again now...
good Luck..
3 of the 4 was having an issue with now work. I had to re-select the alert in the Power BI trigger.
The 4th is a direct query tile in Power BI vs import. I cannot get that to work and it is likely unreleated to this issue.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI Reporting
Hi @sannicolasalex ,
Have you tried updating the connection or re-creating the connection?
Please try doing the following and see if the error still exists:
Hope it helps.
Best Regards,
Thanks @v-bacao-msft , I had tried but without success.
I tried the two proposed ways. The "unauthorized" message still appearing.
Hi @sannicolasalex ,
Please check if the current group to which your current workspace belongs is a public group.
I'm afraid I'm not particularly familiar with Power BI's permissions, but I did the following tests to reproduce your problem and seem to find the cause of the problem.
If the current group is a private group, then the Owner needs to publish the application to share to the specified group or users within the organization, such as you.
Then you can add a new alert rule based on the app that has already shared with you and reconfigure the Flow.
This problem should be solved. Here is a screenshot of the Flow I created:
Best Regards,
Hi again,
I've tried but without success.
Notes:
I am administrator of the group.
I am the owner of the dashboard.
I've created a new app and a test alert to try this and still failing.
What else to do?
Update
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.