Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Ask the Fabric Databases & App Development teams anything! Live on Reddit on August 26th. Learn more.

Reply
MarkBurgess
Advocate I
Advocate I

Copy job orchestration and error handling

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?

1 ACCEPTED SOLUTION
MarkBurgess
Advocate I
Advocate I

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

MarkBurgess_0-1753689794994.png

Microsoft Fabric Roadmap

View solution in original post

3 REPLIES 3
smeetsh
Helper V
Helper V

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
Microsoft Employee
Microsoft Employee

Thanks

MarkBurgess
Advocate I
Advocate I

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

MarkBurgess_0-1753689794994.png

Microsoft Fabric Roadmap

Helpful resources

Announcements
Fabric July 2025 Monthly Update Carousel

Fabric Monthly Update - July 2025

Check out the July 2025 Fabric update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors
Top Kudoed Authors