Fabric Dataflow Gen2 Job

The Fabric Dataflow Gen2 job type triggers a Microsoft Fabric Dataflow Gen2 item via POST /workspaces/{wsId}/items/{itemId}/jobs/instances?jobType=Dataflow. The dataflow 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 Dataflow.
Job Type — Fabric Dataflow Gen2 (set automatically on import).

Job discovery

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

Parameter handling

The Fabric Dataflow API does not accept run-time parameters — Polysync sends an empty executionData:

{
  "executionData": {}
}

Direction	Sent in `jobs/instances`	Updated from response
(all)	❌ (not supported)	❌ (not supported)

Polysync still lets you define parameters on the Job for documentation, but they are not forwarded. Parameterize the Dataflow's source connections via Fabric variables instead.

Execution flow

Same as Fabric Notebook:

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

Monitor URL

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

Best practices

Treat the Dataflow Job as a trigger — schedule it from Polysync, but configure its sources / destinations / variables in Fabric.
Pair the Dataflow Job with a downstream Notebook or Pipeline Job in Polysync if you need parameterization of the downstream work.

Troubleshooting

Polysync parameter value seemingly ignored — that's expected; the Fabric Dataflow endpoint silently discards executionData.parameters.

Documentation