When you activate the media processing service, the system will automatically create a user queue (queue-1) for you. When you submit a job, the job will be arranged in the queue first and executed in sequence according to the priority and order of submission. You can also set a callback rule to stay up to date with the job or workflow progress, and the system will send the processing result and status information to the specified address.
Currently, CI supports only one queue. If you want more concurrent queues, submit a ticket for assistance.
You can enable or pause a queue in its Operation column.
- After the queue is paused, you cannot use the job and workflow features in the console.
- After the queue is paused, jobs in it will stop.
CI supports user-defined callback URLs. After an event is completed, the system sends an HTTP POST request whose body contains notification content to a user-defined callback URL. You can use the configured callback URL to learn about the processing progress and status so that you can perform other operations as needed.
After a job is completed, the system will send the following callback content to the configured callback URL:
<Response> <JobsDetail></JobsDetail> <NonExistJobIds></NonExistJobIds> </Response>
The nodes are as described below:
|JobsDetail||Job details. Same as Response.JobsDetail in
|NonExistJobIds||List of non-existing job IDs queried. If all jobs exist, this node will not be returned.||String|