Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hello everyone,
I have created a Pipeline in Fabric and I want to store in a table named "PipelineOrchestrator_Bronz_Execution_Logs" some statistics related to each time I run this pipeline. I can trigger in two ways: manually or schedulling it daily at a determined time.
One of the variables I'm trying to store is the TriggerType which is a system variable. To do this, I am using a SCRIPT activity which inserts this data into the aforementioned table (See picture below)
When I manually trigger this pipeline I get the value "Manual". However, the problem happens when the scheduler runs it. Instead of getting "ScheduleTrigger" value, I still get "Manual"
Does someone know if I am doing something incorrectly?
Solved! Go to Solution.
Hi @iurdiain ,
Thanks for reaching out to the Microsoft fabric community forum.
It appears that Fabric pipelines may not support PipelineTriggerType in the same way Azure Data Factory does, as there is no mention of it in the official documentation. This suggests that the functionality might not be currently available in Fabric.
These are the system variables that are supported in Fabric pipeline
Reference article: Expressions and functions - Microsoft Fabric | Microsoft Learn
As a workaround, to reliably capture the trigger type in a Microsoft Fabric pipeline, it's recommended to pass it explicitly as a parameter from the trigger to the pipeline. To do this, start by defining a pipeline parameter named TriggerType. When setting up your trigger—such as a scheduled trigger—assign a value to this parameter, for example "ScheduleTrigger". Inside your pipeline, you can then access this value using @pipeline().parameters.TriggerType. Finally, use this value in your SCRIPT activity to log the trigger type into your PipelineOrchestrator_Bronz_Execution_Logs table. This method ensures consistent and accurate tracking of how your pipeline was initiated, whether manually or by schedule.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thanks and Regards
Hi @iurdiain ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the community members for the issue worked. If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Thanks and regards
Hi @iurdiain
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If our responses has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @iurdiain,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @iurdiain ,
Thanks for reaching out to the Microsoft fabric community forum.
It appears that Fabric pipelines may not support PipelineTriggerType in the same way Azure Data Factory does, as there is no mention of it in the official documentation. This suggests that the functionality might not be currently available in Fabric.
These are the system variables that are supported in Fabric pipeline
Reference article: Expressions and functions - Microsoft Fabric | Microsoft Learn
As a workaround, to reliably capture the trigger type in a Microsoft Fabric pipeline, it's recommended to pass it explicitly as a parameter from the trigger to the pipeline. To do this, start by defining a pipeline parameter named TriggerType. When setting up your trigger—such as a scheduled trigger—assign a value to this parameter, for example "ScheduleTrigger". Inside your pipeline, you can then access this value using @pipeline().parameters.TriggerType. Finally, use this value in your SCRIPT activity to log the trigger type into your PipelineOrchestrator_Bronz_Execution_Logs table. This method ensures consistent and accurate tracking of how your pipeline was initiated, whether manually or by schedule.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thanks and Regards
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
9 | |
5 | |
4 | |
3 | |
3 |