<?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: Serving Endpoint Disappears After One Day in Machine Learning</title>
    <link>https://community.databricks.com/t5/machine-learning/serving-endpoint-disappears-after-one-day/m-p/124754#M4151</link>
    <description>&lt;P&gt;If your endpoint is tied to a model in MLflow Registry, and that model is archived or deleted, it could cause the endpoint to disappear.&amp;nbsp;so please check if the registered model/version still exists.&lt;/P&gt;</description>
    <pubDate>Thu, 10 Jul 2025 07:50:26 GMT</pubDate>
    <dc:creator>altafamber</dc:creator>
    <dc:date>2025-07-10T07:50:26Z</dc:date>
    <item>
      <title>Serving Endpoint Disappears After One Day</title>
      <link>https://community.databricks.com/t5/machine-learning/serving-endpoint-disappears-after-one-day/m-p/124745#M4150</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I'm encountering an issue where a serving endpoint I create disappears from the list of serving endpoints after a day. This has happened both when I created the endpoint from the Databricks UI and using the Databricks SDK.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2025 07:37:34 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/serving-endpoint-disappears-after-one-day/m-p/124745#M4150</guid>
      <dc:creator>prashant_089</dc:creator>
      <dc:date>2025-07-10T07:37:34Z</dc:date>
    </item>
    <item>
      <title>Re: Serving Endpoint Disappears After One Day</title>
      <link>https://community.databricks.com/t5/machine-learning/serving-endpoint-disappears-after-one-day/m-p/124754#M4151</link>
      <description>&lt;P&gt;If your endpoint is tied to a model in MLflow Registry, and that model is archived or deleted, it could cause the endpoint to disappear.&amp;nbsp;so please check if the registered model/version still exists.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2025 07:50:26 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/serving-endpoint-disappears-after-one-day/m-p/124754#M4151</guid>
      <dc:creator>altafamber</dc:creator>
      <dc:date>2025-07-10T07:50:26Z</dc:date>
    </item>
    <item>
      <title>Re: Serving Endpoint Disappears After One Day</title>
      <link>https://community.databricks.com/t5/machine-learning/serving-endpoint-disappears-after-one-day/m-p/124765#M4152</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Yes, those models are registered in Unity Catalog and have not been deleted.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2025 08:35:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/serving-endpoint-disappears-after-one-day/m-p/124765#M4152</guid>
      <dc:creator>prashant_089</dc:creator>
      <dc:date>2025-07-10T08:35:50Z</dc:date>
    </item>
    <item>
      <title>Re: Serving Endpoint Disappears After One Day</title>
      <link>https://community.databricks.com/t5/machine-learning/serving-endpoint-disappears-after-one-day/m-p/134452#M4347</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/174523"&gt;@prashant_089&lt;/a&gt;&amp;nbsp;, what you are experiencing should not happen on its own except for some extremely outlying circumstanctes.&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;IF YOU ARE USING Databricks Free Edition&lt;/STRONG&gt; you shold ignore everything below.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Here are some troubleshooting suggestions/tips:&lt;/P&gt;
&lt;H3 class="_7uu25p0 qt3gz9c _7pq7t612 heading3 _7uu25p1"&gt;Likely causes to check first&lt;/H3&gt;
&lt;P class="qt3gz91 paragraph"&gt;&lt;STRONG&gt;Workspace disabled/suspended or canceled&lt;/STRONG&gt;: When a workspace is disabled or canceled (including transient off/on patterns), the platform can automatically delete serving endpoints. We’ve seen concrete cases where daily subscription toggling resulted in endpoint deletion, with no user-driven delete in audit logs.&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;&lt;STRONG&gt;Trial or compliance restrictions&lt;/STRONG&gt;: If the customer is on a &lt;STRONG&gt;time‑based trial&lt;/STRONG&gt; or a compliance-restricted workspace (HIPAA/SHIELD/FedRAMP), serving may be disabled via SAFE flags. As part of enforcement, endpoints are deleted by the NOC process when serving is turned off.&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;&lt;STRONG&gt;“Scale to zero” does not delete endpoints&lt;/STRONG&gt;: The &lt;STRONG&gt;scale_to_zero_enabled&lt;/STRONG&gt; flag only stops compute when idle; it does not remove the endpoint. Deletion requires an explicit delete, policy enforcement, or workspace lifecycle event.&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;&lt;STRONG&gt;Some things to test:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;&lt;STRONG&gt;Confirm via REST GET&lt;/STRONG&gt; whether the endpoint still exists. If it’s truly deleted, GET returns 404; if it’s stopped or updating, you’ll get a response and can start it.&lt;/P&gt;
&lt;DIV class="go8b9g1 _7pq7t6cc"&gt;
&lt;PRE&gt;&lt;CODE class="markdown-code-bash qt3gz9e hljs language-bash _1ymogdh2"&gt;&lt;SPAN class="hljs-comment"&gt;# Replace URL, token, and endpoint name&lt;/SPAN&gt;
curl -s -H &lt;SPAN class="hljs-string"&gt;"Authorization: Bearer &lt;SPAN class="hljs-variable"&gt;$DATABRICKS_TOKEN&lt;/SPAN&gt;"&lt;/SPAN&gt; \
  https://&amp;lt;workspace-host&amp;gt;/api/2.0/serving-endpoints/&amp;lt;ENDPOINT_NAME&amp;gt;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/DIV&gt;
&lt;P class="qt3gz91 paragraph"&gt;If this returns 404 Not Found, the endpoint was deleted. If it returns JSON with &lt;CODE class="qt3gz9f"&gt;state&lt;/CODE&gt;, the endpoint still exists (possibly stopped).&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;&lt;STRONG&gt;Query Audit Logs&lt;/STRONG&gt; for a &lt;CODE class="qt3gz9f"&gt;deleteServingEndpoint&lt;/CODE&gt; event around the disappearance window. Model Serving writes audit events under &lt;CODE class="qt3gz9f"&gt;serverlessRealTimeInference&lt;/CODE&gt; with the endpoint name in request params.&lt;/P&gt;
&lt;DIV class="go8b9g1 _7pq7t6cc"&gt;
&lt;PRE&gt;&lt;CODE class="markdown-code-sql qt3gz9e hljs language-sql _1ymogdh2"&gt;&lt;SPAN class="hljs-comment"&gt;-- Replace endpoint name and time bounds&lt;/SPAN&gt;
&lt;SPAN class="hljs-keyword"&gt;SELECT&lt;/SPAN&gt;
  &lt;SPAN class="hljs-type"&gt;timestamp&lt;/SPAN&gt;,
  service,
  action,
  request_params,
  user_identity
&lt;SPAN class="hljs-keyword"&gt;FROM&lt;/SPAN&gt; system.access.audit
&lt;SPAN class="hljs-keyword"&gt;WHERE&lt;/SPAN&gt; service &lt;SPAN class="hljs-operator"&gt;=&lt;/SPAN&gt; &lt;SPAN class="hljs-string"&gt;'serverlessRealTimeInference'&lt;/SPAN&gt;
  &lt;SPAN class="hljs-keyword"&gt;AND&lt;/SPAN&gt; action &lt;SPAN class="hljs-operator"&gt;=&lt;/SPAN&gt; &lt;SPAN class="hljs-string"&gt;'deleteServingEndpoint'&lt;/SPAN&gt;
  &lt;SPAN class="hljs-keyword"&gt;AND&lt;/SPAN&gt; (request_params:name &lt;SPAN class="hljs-operator"&gt;=&lt;/SPAN&gt; &lt;SPAN class="hljs-string"&gt;'&amp;lt;ENDPOINT_NAME&amp;gt;'&lt;/SPAN&gt; &lt;SPAN class="hljs-keyword"&gt;OR&lt;/SPAN&gt; request_params &lt;SPAN class="hljs-keyword"&gt;LIKE&lt;/SPAN&gt; &lt;SPAN class="hljs-string"&gt;'%&amp;lt;ENDPOINT_NAME&amp;gt;%'&lt;/SPAN&gt;)
  &lt;SPAN class="hljs-keyword"&gt;AND&lt;/SPAN&gt; &lt;SPAN class="hljs-type"&gt;timestamp&lt;/SPAN&gt; &lt;SPAN class="hljs-keyword"&gt;BETWEEN&lt;/SPAN&gt; &lt;SPAN class="hljs-type"&gt;TIMESTAMP&lt;/SPAN&gt;(&lt;SPAN class="hljs-string"&gt;'&amp;lt;START&amp;gt;'&lt;/SPAN&gt;) &lt;SPAN class="hljs-keyword"&gt;AND&lt;/SPAN&gt; &lt;SPAN class="hljs-type"&gt;TIMESTAMP&lt;/SPAN&gt;(&lt;SPAN class="hljs-string"&gt;'&amp;lt;END&amp;gt;'&lt;/SPAN&gt;)
&lt;SPAN class="hljs-keyword"&gt;ORDER&lt;/SPAN&gt; &lt;SPAN class="hljs-keyword"&gt;BY&lt;/SPAN&gt; &lt;SPAN class="hljs-type"&gt;timestamp&lt;/SPAN&gt; &lt;SPAN class="hljs-keyword"&gt;DESC&lt;/SPAN&gt;;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/DIV&gt;
&lt;P class="qt3gz91 paragraph"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;&lt;STRONG&gt;Correlate workspace state changes&lt;/STRONG&gt; (disable/enable/suspend) in system tables to the same time window. This helps confirm if deletion was triggered by workspace lifecycle rather than a user/API call.&lt;/P&gt;
&lt;DIV class="go8b9g1 _7pq7t6cc"&gt;
&lt;PRE&gt;&lt;CODE class="markdown-code-sql qt3gz9e hljs language-sql _1ymogdh2"&gt;&lt;SPAN class="hljs-keyword"&gt;SELECT&lt;/SPAN&gt; &lt;SPAN class="hljs-operator"&gt;*&lt;/SPAN&gt;
&lt;SPAN class="hljs-keyword"&gt;FROM&lt;/SPAN&gt; system.access.workspaces_latest
&lt;SPAN class="hljs-keyword"&gt;WHERE&lt;/SPAN&gt; workspace_id &lt;SPAN class="hljs-operator"&gt;=&lt;/SPAN&gt; CURRENT_WORKSPACE()
&lt;SPAN class="hljs-keyword"&gt;ORDER&lt;/SPAN&gt; &lt;SPAN class="hljs-keyword"&gt;BY&lt;/SPAN&gt; updated_at &lt;SPAN class="hljs-keyword"&gt;DESC&lt;/SPAN&gt;;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/DIV&gt;
&lt;H3 class="_7uu25p0 qt3gz9c _7pq7t612 heading3 _7uu25p1"&gt;&amp;nbsp;&lt;/H3&gt;
&lt;H3 class="_7uu25p0 qt3gz9c _7pq7t612 heading3 _7uu25p1"&gt;Quick checklist to run now&lt;/H3&gt;
&lt;P class="qt3gz91 paragraph"&gt;Run the &lt;STRONG&gt;GET endpoint&lt;/STRONG&gt; check to confirm deletion vs. stopped/updating.&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;Query &lt;STRONG&gt;Audit Logs&lt;/STRONG&gt; for &lt;CODE class="qt3gz9f"&gt;deleteServingEndpoint&lt;/CODE&gt; in the relevant window to see if a user/API deletion occurred.&lt;/P&gt;
&lt;DIV class="_7pq7t614 _7pq7t6cc wrz27r2 wrz27r0"&gt;&lt;SPAN class="xh5urp3 xh5urp1 xh5urp0" aria-label="3 sources"&gt;3 sources&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;P class="qt3gz91 paragraph"&gt;Query &lt;STRONG&gt;workspaces_latest&lt;/STRONG&gt; to detect disable/enable/suspend events around the time the endpoint vanished.&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;Determine whether the customer’s workspace is &lt;STRONG&gt;trial or subject to compliance restrictions&lt;/STRONG&gt; that might disable serving; if so, expect enforced deletions until serving is enabled.&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;Best of luck, Louis.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Oct 2025 18:10:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/serving-endpoint-disappears-after-one-day/m-p/134452#M4347</guid>
      <dc:creator>Louis_Frolio</dc:creator>
      <dc:date>2025-10-09T18:10:56Z</dc:date>
    </item>
  </channel>
</rss>

