MetricSign
EN|NLRequest Access
High severityjob

Power BI Refresh Error:
INTERNAL_ERROR

What does this error mean?

The Databricks platform encountered an unexpected internal error. This is not caused by user code — it indicates a fault in the Databricks infrastructure or control plane.

Common causes

  • 1Transient Databricks control plane issue
  • 2Cloud provider (AWS/Azure/GCP) infrastructure fault
  • 3The cluster was terminated by the cloud provider unexpectedly
  • 4A cluster termination code (e.g. COMMUNICATION_LOST) caused the job to fail

How to fix it

  1. 1Check the Databricks status page for active incidents in your region
  2. 2Open the cluster event log to find the cluster termination reason
  3. 3Retry the run — INTERNAL_ERROR is often transient and resolves on retry
  4. 4If it recurs, check for underlying termination codes like COMMUNICATION_LOST or SPOT_INSTANCE_TERMINATION
  5. 5Contact Databricks support with the run ID and cluster ID if retries continue to fail

Frequently asked questions

Should I report INTERNAL_ERROR to Databricks?

If it recurs on the same job after multiple retries, yes. Include the run ID, cluster ID, and the cluster termination error code from the event log.

Is INTERNAL_ERROR always a Databricks bug?

Not always — the underlying cause is often a cluster termination code like SPOT_INSTANCE_TERMINATION or COMMUNICATION_LOST, which can be caused by cloud provider or network issues.

Other job errors