Copy job orchestration and error handling

[MarkBurgess]

Hi, are there any plans to improve the options for scheduling copy jobs? They are immensely useful, but it you want to schedule further transformations off the back of a copy job you just have to assume it'll be done by a certain time. 

I'm also concerned that there is no way to get notified if a copy job fails.

Triggering a copy job from a pipeline would solve all of these problems, is this something that's on the road map?

[smeetsh]

I have solved this by having the next copy job(s) in a separate pipeline and calling that pipeling from the parent pipeline, once it is completed

[saurabh-msft]

Thanks

[MarkBurgess · Accepted solution]

To anyone else wondering, yes it is in the roadmap! My colleague found it:

Microsoft Fabric Roadmap