Error in Power automate flow

(4) Share

Report

Posted on by SD-22081805-0

I have created a flow in power automate and established the connection with servicenow iam getting the error as follows.

Failed to retrieve dynamic inputs. Error details: 'The response from API 'service-now' operation 'GetRecordSchema' with status code '200' does not contain a valid OpenAPI schema object.'

can anyone help in resolving the issue

Categories:

Building flows

I have the same question (0)

All responses (13)

Answers (0)

David_MA 12,982 Super User 2025 Season 2 on at

Like (2)

Report

Please show your flow and the error you are getting. Be sure to show how the ServiceNow action is configured. There are not enough details to provide any advice.

Was this reply helpful? Yes No
SM-22082359-0 2 on at

Like (2)

Report

Hi,
All our flows using Service Now connectors are also failing with same error. FLows were working before but started failing from last 4-5 days. Please suggest the fix as it is impacting our prod flows.

Below is the way to reproduce the error -
1. Service Now connection is successful. But, error is only with Create and update record actions. Listing records is working fine.
Error s being displayed when trying to select the record type.

The dynamic operation request to API 'service-now' operation 'GetRecordSchema' failed with status code 'BadGateway'. Error response: { "error": { "code": 502, "message": "Unable to read the schema - Object reference not set to an instance of an object.", "source": "asia-001.azure-apim.net", "path": "choose\\otherwise\\choose\\when[1]\\choose[1]\\when[1]", "policyId": "", "clientRequestId": "eb94e94c-2c9f-415a-b19a-2b3de6c36e40" } }

The response from API 'service-now' operation 'GetRecordSchema' with status code '200' does not contain a valid OpenAPI schema object

Was this reply helpful? Yes No
DP-23080027-0 4 on at

Like (2)

Report

Hi,

I am also encountering this error, last successful run was on Aug 15th, however the Service now connector is still able to connect.

The error appears to occur whenever the flow tries to invoke the API 'service-now' operation 'GetRecordSchema' .

Nothing has changed in my flow.

Thanks

Was this reply helpful? Yes No
Divyesh_Kotadia 15 on at

Like (1)

Report

Hi Team,

I am facing the same issue. I tried with new connection, flow but result is same.

Failed to retrieve dynamic inputs. Error details: 'The response from API 'service-now' operation 'GetRecordSchema' with status code '200' does not contain a valid OpenAPI schema object.'

After I removed Update Record action it appeared for List Records too.

Please guide.

Regards,

Divyesh

Was this reply helpful? Yes No
nhjelmberg 14 on at

Like (1)

Report

The ServieNow API seems to have changed recently. There is a new parameter "body" that is required for Create Record and Update Record. Unfortunately there is no description for this parameter. If Microsoft could provide an example of a valid Open API schema object we might resolve the issue.

ServiceNow - Connectors | Microsoft Learn

Was this reply helpful? Yes No
MD-23081229-0 6 on at

Like (2)

Report

The same thing happens to us. It's happening with flows that were working correctly and were not modified. The connector accepts the credentials but when I try to save the flow it throws that error.

It even happens to me with flows created from scratch that have a single action to query records from Service Now.

Thanks.

Was this reply helpful? Yes No
DR-23081455-0 2 on at

Like (1)

Report

Same Problem here too

Was this reply helpful? Yes No
MT-23081535-0 2 on at

Like (1)

Report

Same issue for me as well! Has there been any update yet?

Was this reply helpful? Yes No
LHewitt 8 on at

Like (1)

Report

Same here. We've opened a ticket with MS and ServiceNow. According to our SN devs "our instance was upgraded to Vancouver Patch 9 Hot Fix 2a on 8-17-2024" which may have caused the issue. This was the most recent update our SN instance received so if that didn't break it then it's most likely a MS issue.

Was this reply helpful? Yes No
AL-24080436-0 3 on at

Like (2)

Report

Affected as well. Hope this is resolved soon!

Was this reply helpful? Yes No