Stops an asynchronous task.

An asynchronous task (StatefulAsyncInvocation) allows you to manage the states of asynchronous invocations. The asynchronous task feature is more suitable for task scenarios.

Request headers

This operation uses only common request headers. For more information, see Common parameters.

Request syntax

PUT /services/{serviceName[.qualifier]}/functions/{functionName}/stateful-async-invocations/{statefulAsyncInvocationId} HTTP/1.1

Request parameters

Parameter Type Position Required Example Description
serviceName String Path Yes service_name

The name of the service to which the asynchronous task belongs.

functionName String Path Yes function_name

The name of the function to which the asynchronous task belongs.

qualifier String Path No alias

The version or alias of the service to which the asynchronous task belongs.

statefulAsyncInvocationId String Path Yes e026ae92-61e5-472f-b32d-1c9e3c4e****

The ID of the asynchronous task.

Note When you use an SDK to invoke a function, we recommend that you specify a business-related ID to facilitate subsequent operations. For example, you can use the name of a video file as the invocation ID for a video-processing function. After that, you can use the ID to check whether the video file is processed or terminate the processing of the video. The ID must start with a letter or an underscore (_) and can contain letters, digits, underscores (_), and hyphens (-). The ID can be up to 128 characters in length. If you do not specify the ID of the asynchronous invocation, Function Compute automatically generates an ID.

No response parameters.

Examples

Sample requests

PUT /services/{serviceName[.qualifier]}/functions/function_name/stateful-async-invocations/e026ae92-61e5-472f-b32d-1c9e3c4e**** HTTP/1.1
Host:fc-ram.aliyuncs.com
Content-Type:application/json
Common request header

Sample success responses

JSON format 

HTTP/1.1 200 OK