fabric-pipeline-poll

To monitor a Fabric Data Pipeline run, you can poll its status continuously until it reaches a terminal state like Succeeded, Failed, or Cancelled. This approach tracks pipeline execution progress and returns final status details for completed runs.

When a Fabric Pipeline run fails or times out, monitoring stops and surfaces detailed failure information. The terminal state is captured as Failed or Cancelled, providing specific error details to help diagnose issues within the data pipeline workflow.

Yes, you can configure a timeout limit when polling Fabric Pipeline status, such as setting it to 1800 seconds for a dev environment. This prevents indefinite polling by capping the duration the monitor waits for a terminal state.

Continuously polling a Fabric Pipeline is ideal for long-running or scheduled pipeline runs. It ensures workflows complete successfully by checking status until a terminal state is reached, offering insights into any execution failures.

Monitoring Fabric Pipeline runs detects terminal states including Succeeded, Failed, and Cancelled. Once the pipeline run reaches any of these states, the polling process stops and reports the final execution status.