CancelDataFlowTask

更新时间:
复制 MD 格式

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 Pending state.

  • 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.DependencyViolation error.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

  • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

  • API: The API that you can call to perform the action.

  • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

  • Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

    • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.

    • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

  • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.

  • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

nas:CancelDataFlowTask

delete

*DataFlow

acs:nas:{#regionId}:{#accountId}:filesystem/{#filesystemId}

None None

Request parameters

Parameter

Type

Required

Description

Example

FileSystemId

string

Yes

The ID of the file system.

  • For a general-purpose CPFS file system, the ID must start with cpfs-, for example, cpfs-125487****.

  • For a CPFS-EHPC file system, the ID must start with bmcpfs-, for example, bmcpfs-0015****.

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:

  • true: performs a dry run without canceling the task. The system checks the required parameters, request format, business limits, and NAS inventory. If the check fails, the system returns an error. If the check passes, the system returns an HTTP 200 OK response.

  • false (default): sends a regular request and cancels the task after passing the validity check.

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.