Forum Discussion

VinceHe's avatar
VinceHe
Regular Visitor
1 year ago
Solved

Data activator error - Triggering a Notebook on New JSON File

Hello everyone,

I am trying to create a Data Activator that triggers a Notebook every time a new JSON file is added to the Files section of my Lakehouse. For the event type, I have selected: "Microsoft.Fabric.OneLake.File.Created".

As the source, I specified the subfolder within Files where the JSON files are uploaded.

 

However, when setting it up, I consistently encounter the following error:


Error message Request '4a7798ee-32ca-45ad-9927-f91386252469|7787f2|82f4c2d8pdsrgwc00' failed at 2025-04-04T09:50:33.6851327Z: Response status code does not indicate success: 500 (Internal Server Error). ({"Message":"An error has occurred."})

 

Has anyone experienced a similar issue or knows a potential fix? Any help would be greatly appreciated!



 

  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi VinceHe ,

    Thank you for reaching out to Microsoft Fabric Community Forum.

    This issue seems to be more related to the service side rather than a misconfiguration in the setup. However, here are a few steps you can try to troubleshoot the problem:

    -->Double-check that the Data Activator setup matches the exact subfolder structure in the Lakehouse. Even small differences (like casing or extra slashes) can lead to issues.

    -->Make sure the incoming JSON files are properly formatted. Corrupted or non-standard JSON might prevent the event trigger from working as expected.

    -->Verify that you have the correct permissions to access both the Lakehouse and the notebook you're trying to trigger.

    -->Confirm that the notebook exists in the same workspace and is accessible. It’s also worth running the notebook manually to ensure there are no issues within it.

    -->Sometimes, backend updates in Microsoft Fabric can cause temporary problems.

    -->As a final step, try deleting the current setup and recreating the trigger from scratch. This has helped in some cases.

    If none of these steps work, it’s best to raise a support ticket with Microsoft. Don’t forget to include the Request ID from the error message for quicker investigation.
    https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

    If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

    Regards,
    B Manikanteswara Reddy

1 Reply

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi VinceHe ,

    Thank you for reaching out to Microsoft Fabric Community Forum.

    This issue seems to be more related to the service side rather than a misconfiguration in the setup. However, here are a few steps you can try to troubleshoot the problem:

    -->Double-check that the Data Activator setup matches the exact subfolder structure in the Lakehouse. Even small differences (like casing or extra slashes) can lead to issues.

    -->Make sure the incoming JSON files are properly formatted. Corrupted or non-standard JSON might prevent the event trigger from working as expected.

    -->Verify that you have the correct permissions to access both the Lakehouse and the notebook you're trying to trigger.

    -->Confirm that the notebook exists in the same workspace and is accessible. It’s also worth running the notebook manually to ensure there are no issues within it.

    -->Sometimes, backend updates in Microsoft Fabric can cause temporary problems.

    -->As a final step, try deleting the current setup and recreating the trigger from scratch. This has helped in some cases.

    If none of these steps work, it’s best to raise a support ticket with Microsoft. Don’t forget to include the Request ID from the error message for quicker investigation.
    https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

    If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

    Regards,
    B Manikanteswara Reddy