Forum Discussion

jj44's avatar
jj44
Advocate I
4 months ago
Solved

Copy Job - retry failed

Hi all,   I’m looking for some advice / shared experience around pipeline activity timeout and retry behaviour in Fabric. I’ve got a number of pipelines with multiple activities, and I’ve previous...
data engineering
data pipeline
  • deborshi_nag's avatar
    deborshi_nag
    4 months ago

    Hello jj44 

     

    The Fabric Copy Job activity may have timed out, but it is probably still working in the background, processing cleaning-up activities. This processing may take more than 30 secs, so when the retry event kicks in, the concurrency guard stops it from running. 

     

    It is best you give it enough time before retry starts, maybe 1 - 3 mins for small jobs and 3 - 8 minutes for heavy duty copy jobs. 

     

deborshi_nag's avatar
deborshi_nag
Super User
4 months ago

Hello jj44 

 

The Fabric Copy Job activity may have timed out, but it is probably still working in the background, processing cleaning-up activities. This processing may take more than 30 secs, so when the retry event kicks in, the concurrency guard stops it from running. 

 

It is best you give it enough time before retry starts, maybe 1 - 3 mins for small jobs and 3 - 8 minutes for heavy duty copy jobs.