Technical Issue with Databricks Marketplace Lead Notifications

koral — Wed, 09 Apr 2025 09:15:41 GMT

Hi,

We publish listings on the Databricks Marketplace.

Several times a week, we receive a lead notification stating: "db sp has installed 'Etsy Dataset'."
It’s always the same dataset and the same name, so it’s likely a technical error.

Does anyone know how to handle this issue?

Thanks!

Re: Technical Issue with Databricks Marketplace Lead Notifications

mark_ott — Tue, 04 Nov 2025 17:47:25 GMT

Yes, this is a known issue reported by other Databricks Marketplace publishers: receiving frequent lead notifications stating "db sp has installed 'Etsy Dataset'" for the same dataset and name, which suggests an underlying technical error in the lead notification system rather than genuine user interest or installs.

What Is Happening

Multiple vendors have flagged that these leads do not correlate to actual consumer activity and appear to be a recurring, automated event or system glitch instead of real dataset installs.
This may be related to notification logic, misconfigured alerts, or a backend service principal (SP) repeatedly triggering the event unintentionally.

Recommended Actions

Review your notification scheduling and alert frequency settings in Databricks Marketplace and dashboard alerts; there could be misconfigurations causing duplicated or false notifications.
Databricks community posts and documentation suggest adjusting notification frequency settings, such as setting “at most every 1 day” to minimize repeat alerts and ensure only meaningful activity triggers a notice.
If configuration changes do not solve this problem, the most direct route is to file a support case with Databricks. Documentation and user forums recommend officially reporting persistent erroneous notifications, as it may require backend intervention to resolve.

How to File a Support Case

Go to Databricks support resources or your admin dashboard, locate the support or help option, and submit a ticket outlining the issue, including the repeated dataset name, frequency, and your suspicions about it being a technical glitch.
Include all relevant screenshots and timestamps, which will help Databricks support quickly identify the notification root cause.

Community Experience

Several users in Databricks community discussions have encountered similar problems and resolved them via support escalation, not through self-service alone.
There are no known self-service fixes if the issue is on Databricks’ backend, so opening a ticket promptly is recommended.