<?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: BAD_REQUEST: ExperimentIds cannot be empty when checking ACLs in bulk in Machine Learning</title>
    <link>https://community.databricks.com/t5/machine-learning/bad-request-experimentids-cannot-be-empty-when-checking-acls-in/m-p/63995#M3128</link>
    <description>&lt;P&gt;Hello, thx for your reply but it seems to me that this issue lies in Databricks CE UI itself. I have no permission denied error and I can still manually download all experiments from Databricks. I can also access the server with `mlflow.login()` and log in new experiments, but I cannot navigate them on Databricks CE's UI. I tried directly create new experiments using the UI and I asked several friends to try this, but they all encountered the same `&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;BAD_REQUEST: ExperimentIds cannot be empty when checking ACLs in bulk`.&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 18 Mar 2024 13:32:07 GMT</pubDate>
    <dc:creator>stanjs</dc:creator>
    <dc:date>2024-03-18T13:32:07Z</dc:date>
    <item>
      <title>BAD_REQUEST: ExperimentIds cannot be empty when checking ACLs in bulk</title>
      <link>https://community.databricks.com/t5/machine-learning/bad-request-experimentids-cannot-be-empty-when-checking-acls-in/m-p/63830#M3123</link>
      <description>&lt;P&gt;I encountered the error when using Databricks CE to log experiments from mlflow. It worked perfectly fine before, but now I cannot open any of my experiments. I tried clean the cookies, change the browser, and create a new account to manually create a new experiment, but this error persisted. It seems to be a universal issue, how can I resolve that?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2024 13:53:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/bad-request-experimentids-cannot-be-empty-when-checking-acls-in/m-p/63830#M3123</guid>
      <dc:creator>stanjs</dc:creator>
      <dc:date>2024-03-15T13:53:41Z</dc:date>
    </item>
    <item>
      <title>Re: BAD_REQUEST: ExperimentIds cannot be empty when checking ACLs in bulk</title>
      <link>https://community.databricks.com/t5/machine-learning/bad-request-experimentids-cannot-be-empty-when-checking-acls-in/m-p/63995#M3128</link>
      <description>&lt;P&gt;Hello, thx for your reply but it seems to me that this issue lies in Databricks CE UI itself. I have no permission denied error and I can still manually download all experiments from Databricks. I can also access the server with `mlflow.login()` and log in new experiments, but I cannot navigate them on Databricks CE's UI. I tried directly create new experiments using the UI and I asked several friends to try this, but they all encountered the same `&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;BAD_REQUEST: ExperimentIds cannot be empty when checking ACLs in bulk`.&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 18 Mar 2024 13:32:07 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/bad-request-experimentids-cannot-be-empty-when-checking-acls-in/m-p/63995#M3128</guid>
      <dc:creator>stanjs</dc:creator>
      <dc:date>2024-03-18T13:32:07Z</dc:date>
    </item>
  </channel>
</rss>

