Power Platform Community Forum Thread Details

Hi everyone,

I’m trying to trigger an Azure Databricks job from Power Automate using the Azure Databricks connector with OAuth authentication, but the flow fails during testing.
Environment / Setup

Connector Used: Azure Databricks
Authentication Type: OAuth Connection (AAD)
Access Tokens: Disabled by admin (cannot use PAT)

Connection Configuration

Server Hostname:
adb-xxxxxxxx.xx.azuredatabricks.net
HTTP Path (SQL Warehouse):
/sql/1.0/warehouses/xxxxxxxxxxxx

The connection itself is created successfully without errors.

Flow Design
My flow is very simple:

Trigger: Manually trigger a flow
Action: Azure Databricks → Trigger a new job run

The Job ID provided is correct and verified in Databricks.( i have can manage permission to run the job)

Problem
When I save and test the flow, it fails with the following error:
ResponseSwaggerSchemaValidationFailure
The API 'databricks' returned an invalid response for workflow operation 'Trigger_a_new_job_run' of type 'OpenApiConnection'.
Error details:
The API operation 'JobsRunNow' requires the property 'body/error_code' to be of type 'String' but is of type 'Integer'

Observations

OAuth connection is successful
Job ID is valid
Failure occurs only when running the flow
Error appears related to response schema validation, not authentication

Questions

Has anyone encountered this SwaggerSchemaValidationFailure with the Databricks connector?
Does the SQL Warehouse HTTP Path affect job execution APIs like JobsRunNow?
Could this be due to a connector schema mismatch or Databricks API response change?
Is there a recommended approach to trigger Databricks jobs when PAT tokens are disabled?

Any guidance or troubleshooting suggestions would be greatly appreciated.
Thanks in advance!
Uploaded image

Categories:

Using flows

Hi @MS-26021609-0,

It looks like the Job API has recently (article is dated Jan 2026) changed from 2.1 to 2.2:

https://learn.microsoft.com/en-us/azure/databricks/reference/jobs-api-2-2-updates

New trigger job method:

https://docs.databricks.com/api/azure/workspace/jobs/runnow

Legacy one:

https://docs.databricks.com/api/azure/workspace/jobs_21/runnow

That might have affected what is returned by the connector and would explain a mismatch. Maybe you can also reach out in parallel to Power Automate support:

https://www.microsoft.com/en-us/power-platform/products/power-automate/support

Have you tried running the same HTTP request with for example the HTTP action or HTTP with Azure AD action instead? That might be a workaround for now.

Happy to help out 😁

I share more #PowerAutomate and #SharePointOnline content on my Blog, LinkedIn, Bluesky profile or Youtube Channel