Forum Discussion
Advocate IIUnable to Detect Scheduled Trigger Inside Pipeline — @pipeline().TriggerType Always Returns "Manual"
Hi Yazdan ,
Thanks for the clarification now that makes perfect sense.
You're absolutely right: using a static parameter in the schedule trigger is a workaround, not a dynamic solution. Unfortunately, as of now, Microsoft Fabric does not expose the actual trigger type (Schedule, Manual, etc.) as a runtime system property inside the pipeline, even though the Monitor view clearly shows it.
Current Limitation
- @pipeline().TriggerType always returns "Manual", regardless of how the pipeline was triggered.
- There's no built-in dynamic way to detect the trigger source during execution.
Since dynamic detection isn't supported yet, the best next step is to submit or upvote a feature request on Microsoft Fabric Ideas. Here's a suggested summary you could use.
Thanks,
Akhil.
Super UserPlease note that the idea already exists here: Make "Triggered by schedule ID" available through system variables
Hope this helps. If so, please give a Kudos 👍 and mark as Accepted Solution ✔️.
- Yazdan
Great! I voted for this useful feature.
Also, another idea exists here about the type of run, which is very handy when coding in Fabric:Expose actual pipeline trigger type (Manual vs Schedule) as a system property
