Managing job status for related jobs is difficult about azure-sdk-for-media-services

[gtrifonov]

We have notification implementation based on azure queue. It is not real time notification but has been implemented to serve described scenario and avoid polling media service directly. Jim do you have any particular use case details when notification through azure queue is not enough? With azure queue notification you will not be able to track % of progress, but you will get queue message per state change.

[turanuk]

Hi George, yes I'm able to attach an event handler for each job that is submitted, but there isn't a way for me to bridge when jobs are related at a higher level. Let's say I create a thumbnail and an HLS video for an input asset - I want to create this concept of "encoding in progress", which will finish when BOTH jobs finish. Does that make sense?

I could workaround by storing job state/workflow inside a database on my end and checking the db when the state changes, but ideally there's a way to group jobs together.

[bhanuneti]

You may want to look at submitting a multiple tasks job where you can submit a job with more than one task (either parallel or chained), one task for thumbnail and another task for smooth etc. That way job state changes to finished when all the tasks are finished.

[gtrifonov]

Currently we are not targeting to implement notification chaining and workflow management like you described above.As you mentioned it can be done in one layer above Media Service. For now I would recommend to utilize notifications through azure queues or some db layer and build such functionality.