CancelDataFlowTask
Cancels a batch or streaming data flow task that is in the Pending or Executing state.
Operation description
Data flow tasks are supported only on CPFS 2.2.0 or later and CPFS-EHPC 2.4.0 or later. You can view the version information on the file system details page in the console.
You can only cancel data flow tasks that are in the
Pendingstate.It typically takes 5 to 10 minutes to cancel a data flow task. You can call the DescribeDataFlowTasks operation to query the execution status of the task.
You cannot cancel a streaming data flow task if it has running subtasks. Attempting to do so returns an
OperationDenied.DependencyViolationerror.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
nas:CancelDataFlowTask |
delete |
*DataFlow
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| FileSystemId |
string |
Yes |
The ID of the file system.
|
cpfs-099394bd928c**** |
| DataFlowId |
string |
Yes |
The ID of the data flow. |
df-194433a5be31**** |
| TaskId |
string |
Yes |
The ID of the data flow task. |
task-38aa8e890f45**** |
| DryRun |
boolean |
No |
Specifies whether to perform a dry run. A dry run checks for issues such as parameter validity and resource availability without actually canceling the task or incurring charges. Valid values:
|
false |
| ClientToken |
string |
No |
A client token used to ensure request idempotency. Your client should generate a value that is unique across requests. The client token must be an ASCII string no longer than 64 characters. For more information, see How to ensure idempotence. Note
If you do not specify this parameter, the system automatically uses the request ID as the client token. Since the request ID is unique for each request, retries will not be idempotent. |
123e4567-e89b-12d3-a456-42665544**** |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
|||
| RequestId |
string |
The request ID. |
2D69A58F-345C-4FDE-88E4-BF518948**** |
Examples
Success response
JSON format
{
"RequestId": "2D69A58F-345C-4FDE-88E4-BF518948****"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | IllegalCharacters | The parameter contains illegal characters. | The parameter contains illegal characters. |
| 400 | MissingFileSystemId | FileSystemId is mandatory for this action. | |
| 400 | MissingDataFlowId | DataFlowId is mandatory for this action. | |
| 400 | MissingTaskId | TaskId is mandatory for this action. | |
| 403 | OperationDenied.ConflictOperation | The operation is denied due to a conflict with an ongoing operation. | |
| 403 | OperationDenied.DependencyViolation | The operation is denied due to dependancy violation. | |
| 403 | OperationDenied.DataFlowNotSupported | The operation is not supported. | |
| 404 | InvalidFileSystem.NotFound | The specified file system does not exist. | The specified file system does not exist. |
| 404 | InvalidDataFlow.NotFound | The specified data flow does not exist. | |
| 404 | InvalidTaskId.NotFound | The specified task ID does not exist. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.