Skip to main content

Dashboard task for jobs

Use a dashboard task to refresh results on a published Databricks dashboard as part of a job.

Configure a dashboard task​

Before you begin, make sure the dashboard is published and accessible to the user configuring the job. You must have at least CAN VIEW access to the dashboard you want to deploy.

note

The jobs UI displays options dynamically based on other configured settings.

To begin the flow to configure a Dashboard task:

  1. Navigate to the Tasks tab in the Jobs UI. For general instructions, see Create or configure a task.
  2. Enter a Task name.
  3. In the Type drop-down menu, select Dashboard.
  4. In the Dashboard drop-down menu, select the dashboard that you want to update.
  5. (Optional) Choose the SQL warehouse used to refresh the dashboard. If not specified, the task uses the dashboard's default warehouse.
note

You must use a serverless or pro SQL warehouse for dashboard tasks.

  1. In the Subscribers drop-down, choose the users and notification destinations that should receive email updates when the dashboard is refreshed. This list is separate from any subscribers configured through the Dashboards UI or API.
  2. (Optional) To configure Duration threshold, Notifications, or Retries, see Advanced task settings.
  3. Click Save task.
note

Job parameters cannot be passed to a dashboard task. All filters and parameters run with their default values. See Set default filter values.

Dashboard execution and access​

Dashboard access and caching behavior depend on how the dashboard is published:

  • For dashboards published with embedded credentials, viewers access data and compute according to the dashboard publisher’s credentials.
  • For dashboards published without embedded credentials, the identity defined in the job’s Run as setting is used to refresh the dashboard. The Run as setting defaults to the job owner. To change the Run as identity, see Configure identity for job runs. Viewers use their own data and compute permissions to access the dashboard output and cannot view refreshed results generated by the Run as identity.
note

Dashboards with embedded credentials are always updated using the publisher's credentials. You cannot use the Run as setting in the Jobs UI to change the Run as identity.

To learn more about publish settings for dashboards, see Publish a dashboard. To learn more about caching behavior for each access type, see Dataset optimization and caching.

Last updated on