<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Copy Job - retry failed in Data Engineering</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Copy-Job-retry-failed/m-p/5156437#M15973</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/910514"&gt;@jj44&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Apr 2026 11:51:41 GMT</pubDate>
    <dc:creator>deborshi_nag</dc:creator>
    <dc:date>2026-04-23T11:51:41Z</dc:date>
    <item>
      <title>Copy Job - retry failed</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Copy-Job-retry-failed/m-p/5156415#M15968</link>
      <description>&lt;P class=""&gt;&lt;SPAN&gt;Hi all,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;I’m looking for some advice / shared experience around pipeline activity timeout and retry behaviour in Fabric.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;I’ve got a number of pipelines with multiple activities, and I’ve previously run into issues where Copy Job activities appear to hang when left with the default timeout (0.12:00:00). To mitigate that, I’ve reduced timeouts significantly (typically 0.00:10:00) and configured retries (retry = 2, retry interval = 30 seconds).&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;This has generally improved matters, but I’ve recently seen the following error:&lt;/SPAN&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P class=""&gt;&lt;SPAN&gt;"CopyJob execution failed… A job instance of the same job type is already running and this job instance is skipped"&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P class=""&gt;&lt;SPAN&gt;From what I can tell, the timeout/retry logic is working as configured, but it looks like the retry may be kicking in before the previous job has fully terminated in the backend.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;In most cases, the Copy activity itself only takes 2–3 minutes to run, so a 10-minute timeout should be more than sufficient.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;My questions are:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Has anyone else run into this behaviour?&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Is it likely that the retry interval (30 seconds) is too short, and the previous job is still “cleaning up” when the retry starts?&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;What timeout / retry / retry interval settings are people typically using for Copy activities?&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;&lt;SPAN&gt;I’m trying to find a sensible balance between failing fast and avoiding these overlapping job issues.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Any insight would be really appreciated.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks Jeff&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Apr 2026 11:24:59 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Copy-Job-retry-failed/m-p/5156415#M15968</guid>
      <dc:creator>jj44</dc:creator>
      <dc:date>2026-04-23T11:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: Copy Job - retry failed</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Copy-Job-retry-failed/m-p/5156437#M15973</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/910514"&gt;@jj44&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Apr 2026 11:51:41 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Copy-Job-retry-failed/m-p/5156437#M15973</guid>
      <dc:creator>deborshi_nag</dc:creator>
      <dc:date>2026-04-23T11:51:41Z</dc:date>
    </item>
  </channel>
</rss>

