ApsaraVideo Media Processing:Trigger a workflow

Comparison of trigger modes

Mode 1: Automatic trigger

1. Create a workflow and set the trigger mode to automatic trigger. By default, when you create a workflow, its trigger mode is automatic trigger. For more information about how to create a workflow, see Create a workflow.

2. Add a file. The following requirements must be met:

   • The file is not generated by MPS or Intelligent Media Services (IMS). For more information, see the "Files are not generated by MPS or IMS" section of this topic.

   • The file path complies with the path matching rules. For more information, see the "Path matching rules" section of this topic.

   • The file name complies with the file name extension matching rules. For more information, see the "File name extension matching rules" section of this topic.

   • The file is uploaded by calling one of the following API operations of OSS.

     Operation	Description
     PutObject	Uploads an object.
     PostObject	Uploads an object to a specific bucket by using an HTML form.
     CopyObject	Copies an object within a bucket or across buckets in the same region.
     CompleteMultipartUpload	Combines the uploaded parts into an object after all parts of the object are uploaded.
     PutSymlink	Creates a symbolic link for an object, which allows you to access the object by using the symbolic link.

Mode 2: Manual trigger for files under a verified path

1. Create a workflow. Before you add files, you must change the trigger mode of the workflow to manual trigger by calling the UpdateMediaWorkflowTriggerMode operation. For more information about how to create a workflow, see Create a workflow.

2. Add a file. The following requirements must be met:

   • The file path complies with the path matching rules. For more information, see the "Path matching rules" section of this topic.

   • The file name complies with the file name extension matching rules. For more information, see the "File name extension matching rules" section of this topic.

   • The file is uploaded by calling an API operation of OSS of your choice.

3. After you add a file, call the AddMedia operation to specify the file to be processed and the ID of the workflow to be triggered based on your business requirements.

Mode 3: Manual trigger for files under different paths

1. Create a workflow. Before you add files, you must change the trigger mode of the workflow to manual trigger by calling the UpdateMediaWorkflowTriggerMode operation. For more information about how to create a workflow, see Create a workflow.

2. Add a file. The following requirements must be met:

   • The file is stored in the region in which MPS is activated.

   • The file is uploaded by calling an API operation of OSS of your choice.

3. After you add a file, call the AddMedia operation to specify the file to be processed and the ID of the workflow to be triggered based on your business requirements. In addition, set the InputUnbind parameter to false, which specifies that MPS does not check the file against the path matching rules or file name extension matching rules.

File matching rules

Files are not generated by MPS or IMS

If the input path of a workflow is the same as the output path of an MPS or IMS job, files generated by that job cannot trigger the workflow. This prevents cyclic triggering caused by overlapping input and output paths. Example:

The output path of Workflow A and the input path of Workflow B are both http://bucket.oss-cn-hangzhou.aliyuncs.com/A/.

• If the input file http://bucket.oss-cn-hangzhou.aliyuncs.com/A/example.flv is generated by Workflow A, Workflow B cannot be triggered.

• If the input file http://bucket.oss-cn-hangzhou.aliyuncs.com/A/example.flv is directly uploaded to the path http://bucket.oss-cn-hangzhou.aliyuncs.com/A/, Workflow B can be triggered.

Path matching rules

An input file can trigger a workflow only if its path falls under the input path specified for the Input node of the workflow. Example: