<?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: Long Connection Time When Triggering a Notebook in a Pipeline in Pipelines</title>
    <link>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4594301#M7204</link>
    <description>&lt;P&gt;You're right. Do you have any suggestions for a short connection time ?&lt;/P&gt;</description>
    <pubDate>Tue, 04 Mar 2025 06:57:00 GMT</pubDate>
    <dc:creator>ahmetyilmaz</dc:creator>
    <dc:date>2025-03-04T06:57:00Z</dc:date>
    <item>
      <title>Long Connection Time When Triggering a Notebook in a Pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4565425#M7167</link>
      <description>&lt;P&gt;I'm experiencing an issue with long connection times when triggering a notebook within a pipeline in Microsoft Fabric. When running the notebook normally, the connection time is relatively fast after the initial connection is established. However, when the notebook is triggered through a pipeline, a new connection is established every time, which leads to significantly longer connection times.&lt;/P&gt;&lt;P&gt;I have tried using a session tag, but the connection time has not improved. Is there any way to keep the connection to a notebook always open? Or is there a way for the pipeline to connect to the same notebook connection repeatedly to improve the execution speed?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Feb 2025 08:35:59 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4565425#M7167</guid>
      <dc:creator>ahmetyilmaz</dc:creator>
      <dc:date>2025-02-25T08:35:59Z</dc:date>
    </item>
    <item>
      <title>Re: Long Connection Time When Triggering a Notebook in a Pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4585366#M7171</link>
      <description>&lt;LI-CODE lang="markup"&gt;Is there any way to keep the connection to a notebook always open? &lt;/LI-CODE&gt;
&lt;P&gt;That would be much worse for you as you would pay dearly in CUs for keeping notebook sessions open.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 01:19:51 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4585366#M7171</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2025-02-26T01:19:51Z</dc:date>
    </item>
    <item>
      <title>Re: Long Connection Time When Triggering a Notebook in a Pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4594301#M7204</link>
      <description>&lt;P&gt;You're right. Do you have any suggestions for a short connection time ?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Mar 2025 06:57:00 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4594301#M7204</guid>
      <dc:creator>ahmetyilmaz</dc:creator>
      <dc:date>2025-03-04T06:57:00Z</dc:date>
    </item>
    <item>
      <title>Re: Long Connection Time When Triggering a Notebook in a Pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4594816#M7207</link>
      <description>&lt;P&gt;I don't. I don't want to suggest something that costs you lots of money.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Mar 2025 11:47:11 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4594816#M7207</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2025-03-04T11:47:11Z</dc:date>
    </item>
    <item>
      <title>Re: Long Connection Time When Triggering a Notebook in a Pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4640795#M7416</link>
      <description>&lt;P&gt;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="100342" data-lia-user-login="lbendlin" class="lia-mention lia-mention-user"&gt;lbendlin&lt;/a&gt;&amp;nbsp; Hi, do you have a different solution? I still have this problem sometimes. Connection time takes too long.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 10:29:51 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Long-Connection-Time-When-Triggering-a-Notebook-in-a-Pipeline/m-p/4640795#M7416</guid>
      <dc:creator>ahmetyilmaz</dc:creator>
      <dc:date>2025-04-07T10:29:51Z</dc:date>
    </item>
  </channel>
</rss>

