Forum Discussion
Reflex: Error accessing the artifact
Hi Willem. The engineering team has found the cause of the problem. Your Data Activator trigger is not able to connect to your Power BI dataset anymore because the authentication you used at the time that you created the trigger is no longer valid. Specifically, according to the log files, you were authenticated using your local device (e.g. via fingerprint/pin rather than via password), and your AAD tenant admin subsequently disabled your device, which has prevented Data Activator from being able to connect to the dataset. We have noted this situation for our product backlog, and we will look at finding a way to provide error/diagnostic information to users in future when authentication failures occur. In the meantime, if you recreate your trigger in Data Activator, then it should work. Thank you for raising the issue.
Hi James. Thanks for the detailed info, this helps me a lot on different items.
Recreating a trigger in Data Activator works for a few days and then it stops again. In our company we use AVD and the AVD gets killed every night (to save energy en money) and the next morning we get a new/fresh AVD machine. Thats the reason the device/AVD i worked on gets disabled every night.
This is the same problem i have with dataset that stops working after a few days if i activate them from my AVD machine. The workarond is loging on to a server and update the dataset credentials from there. Sorry it did not popped into my mind when the Data Activator trigger stoped working.
By te way, instead of recreating the tigger in Data Activator it would be nice if in the future it would be posible to update the data source credentials for trigger (the same as it is posible to update the credentials for datasets now).
I wil ask our system admins if it would be posible to change something on the authentication side to work with passwords instead of fingerprint/pin.
Again, many thanks for the info.