All Products
Search
Document Center

Cloud Parallel File Storage:ModifyDataFlowAutoRefresh

Last Updated:Dec 03, 2025

Modifies an AutoRefresh configuration of a dataflow.

Operation description

  • This operation is available only to CPFS file systems.
  • Only CPFS V2.2.0 and later support dataflows. You can view the version information on the file system details page in the console.
  • You can modify the AutoRefresh configurations only for the dataflows that are in the Running or Stopped state.
  • It generally takes 2 to 5 minutes to modify an AutoRefresh configuration. You can call the DescribeDataFlows operation to query the task of modifying an AutoRefresh configuration.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • For mandatory resource types, indicate with a prefix of * .
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
nas:ModifyDataFlowAutoRefreshupdate
*FileSystem
acs:nas:{#regionId}:{#accountId}:filesystem/{#filesystemId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
FileSystemIdstringYes

The ID of the file system.

cpfs-099394bd928c****
DataFlowIdstringYes

The ID of the dataflow.

df-194433a5be31****
AutoRefreshPolicystringNo

The automatic update policy. The updated data in the source storage is imported into the CPFS file system based on the policy. The following information is displayed:

  • None: Updated data in the source storage is not automatically imported into the CPFS file system. You can run a dataflow task to import the updated data from the source storage.
  • ImportChanged: Updated data in the source storage is automatically imported into the CPFS file system.
None
AutoRefreshIntervallongNo

The automatic update interval. CPFS checks whether data is updated in the directory at the interval specified by this parameter. If data is updated, CPFS starts an automatic update task. Unit: minute.

Valid values: 5 to 526600. Default value: 10.

10
DryRunbooleanNo

Specifies whether to perform a dry run.

During the dry run, the system checks whether the request parameters are valid and whether the requested resources are available. During the dry run, no fileset quota is canceled and no fee is incurred.

Valid value:

  • true: performs a dry run. The system checks the required parameters, request syntax, service limits, and available Apsara File Storage NAS (NAS) resources. Otherwise, an error message is returned. If the request passes the dry run, the HTTP status code 200 is returned. No value is returned for the FileSystemId parameter.
  • false (default): performs a dry run and sends the request. If the request passes the dry run, a fileset is created.
false
ClientTokenstringNo

The client token that is used to ensure the idempotence of the request. You can use the client to generate the token, but you must make sure that the token is unique among different requests.

The token can contain only ASCII characters and cannot exceed 64 characters in length. 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. The request ID may be different for each request.
123e4567-e89b-12d3-a456-42665544****

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

98696EF0-1607-4E9D-B01D-F20930B6****

Examples

Sample success responses

JSONformat

{
  "RequestId": "98696EF0-1607-4E9D-B01D-F20930B6****"
}

Error codes

HTTP status codeError codeError messageDescription
400IllegalCharactersThe parameter contains illegal characters.The parameter contains illegal characters.
400MissingFileSystemIdFileSystemId is mandatory for this action.-
400MissingDataFlowIdDataFlowId is mandatory for this action.-
403OperationDenied.DependencyViolationThe operation is denied due to dependancy violation.-
403OperationDenied.ConflictOperationThe operation is denied due to a conflict with an ongoing operation.-
403OperationDenied.DataFlowNotSupportedThe operation is not supported.-
404InvalidFileSystem.NotFoundThe specified file system does not exist.The specified file system does not exist.
404InvalidDataFlow.NotFoundThe specified data flow does not exist.-
404InvalidRefreshPolicy.InvalidParameterRefresh policy is invalid.-
404InvalidRefreshInterval.OutOfBoundsRefresh interval is out of bounds.-

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-09-05The Error code has changedView Change Details