You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: help/sources/tutorials/api/update-dataflows.md
+46-44Lines changed: 46 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ This tutorial covers the steps for updating a dataflow, including its basic info
9
9
10
10
>[!TIP]
11
11
>
12
-
>Your source connection and your target connection should be mapped to a single dataflow. You should not update your source and target connections separately, as the changes will not be reflected in their corresponding dataflow. If your use case requires an update of your source and target connections, then you must create a new pair of source and target connections, as well as a new dataflow.
12
+
>Your source connection and your target connection should be mapped to a single dataflow. You should not update your source and target connections separately, as the changes will not be reflected in their corresponding dataflow. If your use case requires an update of your source and target connections, then you must create a new pair of source and target connections, as well as a new dataflow.
13
13
14
14
## Getting started
15
15
@@ -171,7 +171,9 @@ To update your dataflow's run schedule, name, and description, perform a PATCH r
171
171
172
172
>[!IMPORTANT]
173
173
>
174
-
>The `If-Match` header is required when making a PATCH request. The value for this header is the unique version of the connection you want to update. The etag value updates with every successful update of a dataflow.
174
+
>* The `If-Match` header is required when making a PATCH request. The value for this header is the unique version of the connection you want to update. The etag value updates with every successful update of a dataflow.
175
+
>
176
+
>* You cannot updated the `startTime` of a dataflow if the initially scheduled `startTime` has already occurred. This limitation applies to both enabled and disabled dataflows.
175
177
176
178
**API format**
177
179
@@ -185,29 +187,29 @@ The following request updates your flow run schedule, as well as your dataflow's
0 commit comments