When a job hops queues, the values for the settings queue and
priority remain how you set them when you created the job. You
can see the values for the job's post-hop destination and queue priority. The
following tabs provide two options for viewing a job's history and queue
priority.
To see if your job hopped queues by using the MediaConvert console:
-
Open the Jobs
page in the MediaConvert console. -
Select a Job ID.
-
Find the Queue transition section that shows the job priority before and after hopping. That section also shows the epoch Timestamp for when the job hopped, the Source queue, and the Destination queue.
Billing tags for hopped jobs
If you use billing tags on your jobs and set your billing tags source to Queue, the charges for your jobs are always listed under the tags for the submission queue. To track how much you were billed for a job that hops queues, you can set the billing tags source to Job. For more information about using tags to sort your AWS bill, see Setting up AWS Elemental MediaConvert resources for cost allocation through tagging.
Note
Cost allocation based on queue only applies to jobs that run in on-demand queues. When your submission queue is a reserved queue and your job hops to an on-demand queue, the charges for that on-demand job appear in your cost allocation report. If you don't put tags on your reserved queue, those charges appear in the report unsorted.
Listing hopped jobs
When you view your job, MediaConvert displays the queue that you submitted
your job. For example, if you submit a job to Queue1, and it hops
to Queue2, that job appears in lists that are filtered for
Queue1. It doesn't appear in lists filtered for
Queue2.
