Fabric Pipeline Job

The Fabric Pipeline job type runs a Microsoft Fabric Data Pipeline item via POST /workspaces/{wsId}/items/{itemId}/jobs/instances?jobType=Pipeline. The pipeline is identified by its item ID — Polysync stores that ID in the Job's External Id.

This job type is supported on the Microsoft Fabric platform.

Required job fields

External Id — the Fabric item ID (GUID) of the Data Pipeline.
Job Type — Fabric Pipeline (set automatically on import).

Job discovery

GET /workspaces/{workspaceId}/items?type=DataPipeline (paginated).

Parameter handling

Input + Input&Output parameters are sent as a flat key-value map:

{
  "executionData": {
    "parameters": {
      "<name1>": "<value1>",
      "<name2>": "<value2>"
    }
  }
}

Direction	Sent in `jobs/instances`	Updated from response
`Input`	✅	❌
`Output`	❌	❌ (not supported)
`Input&Output`	✅	❌ (not supported)

Output parameters are not supported.

Unlike Fabric Notebook, the Pipeline endpoint does not accept a per-parameter type field — the pipeline definition coerces values based on its declared parameter types.

Execution flow

Same as Fabric Notebook:

POST jobs/instances?jobType=Pipeline.
Poll GET .../jobs/instances/{instanceId} (same status table).
Cancel via POST /jobs/instances/{instanceId}/cancel.

Monitor URL

https://app.fabric.microsoft.com/groups/{workspaceId}/datapipelines/{itemId}

Best practices

Match Polysync parameter names exactly to the Pipeline's declared parameters — extra keys are silently ignored by Fabric.

Troubleshooting

Parameter shows as default value in run log — name mismatch between the Polysync parameter and the pipeline declaration; re-import to pull the correct parameter list.

Documentation