Forum Discussion
Unable to create an activator with file creation trigger on OneLake
Hi!
I'm currently trying to set up an activator in one of my worksapces, the capacity it's on is an F64 in UK south, and the lakehouse is in the same workspace and located in UK sout, I can create the activator but not the trigger event, I'm getting the following error:
Failed Request failed with status code 400 CorrelationId: fcaa573a-39a3-49d8-ad14-bc2a1caba2a0 Action: triggerPane.ingestFabricSystemEvents Type: FabricOneLakeEvents
I have tried this across many workspaces and in workspaces it has worked in previously, I'm beginning to believe something might be wrong on the Microsoft side.
Anyone else able to create one?
Hi nnshr,
Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to deborshi_nag for prompt and helpful responses.
Since the issue is occurring across multiple workspaces, including ones where it previously worked, it may not be related to a specific workspace configuration. As part of troubleshooting, you may want to verify that the capacity, workspace, and Lakehouse are all in the same region, confirm that the F64 capacity is active and healthy, and ensure you have sufficient permissions (Contributor or higher) in the workspace.
Regards,
Prasanna Kumar
4 Replies
Hello nnshr I have checked Service Status and Known Issues pages for Fabric, and there's nothing that indicate an issue. I have also checked Activator for OneLake events in my workspace where capacity is UK South, all working as expected. I don't think it is anything to do with Fabric service.
Can you let me know what what stage do you get that error above?
Hi nnshr,
Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to deborshi_nag for prompt and helpful responses.
Since the issue is occurring across multiple workspaces, including ones where it previously worked, it may not be related to a specific workspace configuration. As part of troubleshooting, you may want to verify that the capacity, workspace, and Lakehouse are all in the same region, confirm that the F64 capacity is active and healthy, and ensure you have sufficient permissions (Contributor or higher) in the workspace.
Regards,
Prasanna KumarHi nnshr,
Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.
Best regards,
Prasanna KumarHi @nnshr,
Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.
Best regards,
Prasanna Kumar
