<?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 Widget value not synchronized after detach/reattach in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/widget-value-not-synchronized-after-detach-reattach/m-p/124890#M47285</link>
    <description>&lt;P&gt;Hello Databricks Team,&lt;/P&gt;&lt;P&gt;I hope you are doing well.&lt;/P&gt;&lt;P&gt;I’m working with dbutils.widgets in a Databricks notebook using the Accessed Commands mode, and I have encountered some challenges.&lt;/P&gt;&lt;P&gt;Specifically, after detaching and reattaching to the cluster:&lt;BR /&gt;- the widgets remain visible in the UI;&lt;BR /&gt;- however, their values are no longer properly synchronized with the backend;&lt;BR /&gt;- Accessed Commands do not automatically trigger when widget values are changed;&lt;BR /&gt;- and in the code, we continue to see the old value, even though the UI shows the updated one.&lt;/P&gt;&lt;P&gt;What we have tried:&lt;BR /&gt;- Using Run Notebook mode, but this is not suitable as it executes the entire notebook, whereas we only want specific cells to run.&lt;BR /&gt;- Using Do Nothing mode, but this requires manual cell execution, which we want to avoid.&lt;BR /&gt;- We have also considered switching to ipywidgets, but are concerned about potential instability or synchronization issues, especially after reattaching.&lt;/P&gt;&lt;P&gt;Our goal:&lt;BR /&gt;- Ensure that after detaching/reattaching and changing a widget value, only the relevant cells (Accessed Commands) are executed.&lt;BR /&gt;- Make sure the code consistently picks up the updated widget value, without requiring a full notebook rerun or manual intervention.&lt;/P&gt;&lt;P&gt;I would be grateful if you could let us know:&lt;BR /&gt;- Is this a known limitation of Databricks widgets?&lt;BR /&gt;- Are there any recommended workarounds or best practices to achieve this behavior?&lt;/P&gt;&lt;P&gt;Thank you very much for your time and support.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;</description>
    <pubDate>Fri, 11 Jul 2025 11:11:33 GMT</pubDate>
    <dc:creator>varni</dc:creator>
    <dc:date>2025-07-11T11:11:33Z</dc:date>
    <item>
      <title>Widget value not synchronized after detach/reattach</title>
      <link>https://community.databricks.com/t5/data-engineering/widget-value-not-synchronized-after-detach-reattach/m-p/124890#M47285</link>
      <description>&lt;P&gt;Hello Databricks Team,&lt;/P&gt;&lt;P&gt;I hope you are doing well.&lt;/P&gt;&lt;P&gt;I’m working with dbutils.widgets in a Databricks notebook using the Accessed Commands mode, and I have encountered some challenges.&lt;/P&gt;&lt;P&gt;Specifically, after detaching and reattaching to the cluster:&lt;BR /&gt;- the widgets remain visible in the UI;&lt;BR /&gt;- however, their values are no longer properly synchronized with the backend;&lt;BR /&gt;- Accessed Commands do not automatically trigger when widget values are changed;&lt;BR /&gt;- and in the code, we continue to see the old value, even though the UI shows the updated one.&lt;/P&gt;&lt;P&gt;What we have tried:&lt;BR /&gt;- Using Run Notebook mode, but this is not suitable as it executes the entire notebook, whereas we only want specific cells to run.&lt;BR /&gt;- Using Do Nothing mode, but this requires manual cell execution, which we want to avoid.&lt;BR /&gt;- We have also considered switching to ipywidgets, but are concerned about potential instability or synchronization issues, especially after reattaching.&lt;/P&gt;&lt;P&gt;Our goal:&lt;BR /&gt;- Ensure that after detaching/reattaching and changing a widget value, only the relevant cells (Accessed Commands) are executed.&lt;BR /&gt;- Make sure the code consistently picks up the updated widget value, without requiring a full notebook rerun or manual intervention.&lt;/P&gt;&lt;P&gt;I would be grateful if you could let us know:&lt;BR /&gt;- Is this a known limitation of Databricks widgets?&lt;BR /&gt;- Are there any recommended workarounds or best practices to achieve this behavior?&lt;/P&gt;&lt;P&gt;Thank you very much for your time and support.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jul 2025 11:11:33 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/widget-value-not-synchronized-after-detach-reattach/m-p/124890#M47285</guid>
      <dc:creator>varni</dc:creator>
      <dc:date>2025-07-11T11:11:33Z</dc:date>
    </item>
    <item>
      <title>Re: Widget value not synchronized after detach/reattach</title>
      <link>https://community.databricks.com/t5/data-engineering/widget-value-not-synchronized-after-detach-reattach/m-p/125027#M47325</link>
      <description>&lt;P&gt;Hello there&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please share the code used for widgets?&lt;/P&gt;&lt;P&gt;also if you change mannually, is it working? (did it worked before?)&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you trying to load via some parent notebook?&lt;/P&gt;&lt;P&gt;Waiting for your response.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 13 Jul 2025 06:54:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/widget-value-not-synchronized-after-detach-reattach/m-p/125027#M47325</guid>
      <dc:creator>Khaja_Zaffer</dc:creator>
      <dc:date>2025-07-13T06:54:56Z</dc:date>
    </item>
  </channel>
</rss>

