Forum Discussion
Fabric Activator not activating
After I've changed my account password but reconnected every connections, my activator seems to not get activated.
The activation condition is when in my lakehouse (onelake), a file is replaced, it will trigger the activator to activate and then to run the pipeline. However, no matter how many times I replace the file via API, or manually deleting and creating the file, the activator always show no data.
I can confirm that the activator is connected to the lakehouse I am referring to. And I can confirm that I've tested replacing, deleting, adding files via upload and nothing triggers. It just seems like the connection between the activator and the lakehouse is not there. The error message shows this:
{
"itemId": "",
"correlationId": "fff6072f-a1f0-4c1e-aaaa-ba4ac974b55b",
"errorMessage": "Request failed with status code 500",
"timestamp": "2025-06-19T09:58:48.547Z"
}
{
"itemId": "9c9cf20c-8204-4633-b397-4240a73a75ac",
"correlationId": "ae215f6b-b0dc-4ae7-a023-8a625a5380ad",
"customPayload": {
"code": "DataNotAvailable",
"message": "Unable to process the request. The queried data is not available."
},
"errorMessage": "Request failed with status code 400",
"timestamp": "2025-06-19T09:59:23.464Z"
}
It was connection error. Although I checked that all the required connections are online in the settings page, and reauthorised, in the data pipeline itself, I was required to reconnect all the connections by activity one by one. Basically, how I did it was, I just ran the pipeline, it says failed due to unauthorised activity at which activity, and then I go to that activity and presh refresh and run it, untill all the pipeline is able to run as normal, the activator then came back to work and start being trigerred once I trigger it.
6 Replies
I've also made sure that the connection is online between fabric and one lake lakehouse:
- burakkaragoz
Super User
Hi emilylo ,
Thanks for sharing the details. Based on the error messages you're seeing (500 and 400 with DataNotAvailable), it looks like the Fabric Activator is trying to fetch some metadata or config that either doesn't exist yet or isn't accessible at the time of activation.
A couple of things you might want to check:
Lakehouse readiness: Make sure the "QF L1 Lakehouse" is fully initialized and accessible. Sometimes if it's just been created, it might not be ready for event subscriptions right away.
Permissions: Double-check that the identity running the activator has proper access to the lakehouse and the OneLake events. Lack of permissions can cause these kinds of failures.
Event types: The event types listed look fine, but try removing and re-adding them one by one to see if a specific one is causing the issue.
Try a fresh setup: If nothing works, try deleting the activator and setting it up again from scratch. Sometimes the internal state gets stuck.
Let me know what you find, happy to dig deeper if needed.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
Hi burakkaragoz ,
Thanks for the rapid response.
1. This lakehouse has been initialised and up and running for a couple of weeks. Before I've changed my account password, the previous activator and this lakehouse were working fine.
2. I'm suspecting this might be related to permission issue as ever since I've changed my password, this activator stops working. I can still access the lakehouse. But happy to dig further regarding this problem. If you can let me know how do I double check my permissions needed to make the activator works, that would be great.
3. Tried.
4. Tried.
Thank you!
v-prasareCommunity Support
In this scenario i suggest you to raise a support ticket here. so, that they can assit you in addressing the issue you are facing. please follow below link on how to raise a support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
- v-prasare
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.
Thank you for your understanding and participation.
It was connection error. Although I checked that all the required connections are online in the settings page, and reauthorised, in the data pipeline itself, I was required to reconnect all the connections by activity one by one. Basically, how I did it was, I just ran the pipeline, it says failed due to unauthorised activity at which activity, and then I go to that activity and presh refresh and run it, untill all the pipeline is able to run as normal, the activator then came back to work and start being trigerred once I trigger it.
