Forum Discussion
Query activity runs REST API
Hi Elagunas
This is a current gap in the public API. queryactivityruns doesn’t populate output for in-progress activities (e.g., Invoke/Execute Pipeline), so the child pipelineRunId is null until the parent activity finishes. The portal shows it via internal telemetry that the API doesn’t expose mid-run.
(1) Poll until the parent completes, then call query activity runs again;
(2) Have the child pipeline log/send its @pipeline().RunId at start (to KQL/SQL/Lakehouse/webhook) for live tracking.
https://learn.microsoft.com/en-us/fabric/data-factory/pipeline-rest-api-capabilities
Super UserHi Elagunas
This is a current gap in the public API. queryactivityruns doesn’t populate output for in-progress activities (e.g., Invoke/Execute Pipeline), so the child pipelineRunId is null until the parent activity finishes. The portal shows it via internal telemetry that the API doesn’t expose mid-run.
(1) Poll until the parent completes, then call query activity runs again;
(2) Have the child pipeline log/send its @pipeline().RunId at start (to KQL/SQL/Lakehouse/webhook) for live tracking.
https://learn.microsoft.com/en-us/fabric/data-factory/pipeline-rest-api-capabilities