The short video below walks through the Data Plane area: filtering the task list by queue and status, opening a task to see its details, retrying a failed task, and exporting the task list.
The Data Plane area lets you monitor and manage the video processing that turns ingested content into ready-to-stream assets. It covers two kinds of work: transcoding, which converts source video into the required formats and bitrates, and packaging, which prepares the transcoded video for delivery to viewers.
From here you can watch tasks move through the queue, spot tasks that have failed, look into why, and retry them. This is the place to go when the Overview shows a large or paused queue.
The module is opened from the sidebar under VOD Management > Data Plane Queues > Tasks. You can also reach it by clicking a queue card on the Overview.
The main screen shows a table of processing tasks. The typical columns are:
Content Title: the title of the content being processed.
Enqueue Time: when the task was added to the queue.
Status: the current state of the task (see "Task statuses" below).
Type: whether the task is Transcoding or Packaging.
Priority: the task's place in the queue, with higher-priority tasks worked on first.
Package Asset ID, Video Asset ID and Provider ID: identifiers that link the task back to the content and its source.
You can also work with the list in several ways:
Filter by queue using the buttons at the top (All Types, Packaging or Transcoding).
Filter by status, for example to show only failed tasks.
Choose a time range, for example the last 24 hours or a custom range.
Search by title or task identifier.
Sort by clicking a column header, and show or hide columns to suit your work.
Refresh the list to see the latest state (it also updates on its own).
Each task shows a status so you can see at a glance where it is:
Pending: queued and waiting to be processed.
In Progress: currently being processed.
Completed: finished successfully.
Failed: did not complete, so check the details to see why.
Paused: the task or its queue has been temporarily halted.
Click a task row to open a side panel with more detail: the task's identifiers, its status and timings, the content it relates to, the parent job it belongs to, and any logs or events recorded during processing. For a failed task, this is where you find out what went wrong before deciding to retry it.
Filter the list by the Failed status to find tasks that need attention.
Select one or more failed tasks.
Use the Retry DP Task action to reprocess them. This action is available if you have the required permission, and you must select at least one task first.
Watch the status change as the tasks are picked up again – typically from Failed back to Pending, then In Progress, and finally Completed.
Retrying often clears failures caused by temporary problems, so it is usually worth retrying a failed task promptly.
Where you have the required permission, you can influence how quickly the queue is processed – for example adjusting the rate at which tasks are consumed, or pausing and resuming processing. Pausing a queue stops new tasks being processed until you resume it, and a paused queue is flagged on the Overview dashboard.
Use the Export action to download the current task list to a file for reporting or offline analysis – for example to track processing times or review failures over a period. Exports are limited to a maximum number of rows, so narrow the list with filters before exporting a large set.
Arrive from the Overview after noticing a large or paused queue.
Filter to the queue and status you care about, often Failed tasks first.
Open a failing task to understand the cause.
Select the affected tasks and retry them.
Watch the statuses progress to Completed, and export a report if you need one.
A steadily growing queue of Pending tasks is the clearest sign that processing is falling behind, so keep an eye on it.
Retry failed tasks early, because many failures are temporary and clear on the first retry.
Open a task and read its details before retrying, so you understand whether the cause was transient or needs a different fix.
A paused queue will not process new content until it is resumed, so if content is stuck, check for a paused queue here and on the Overview.
Narrow the list with filters before exporting, as exports are capped at a maximum number of rows.
