Fin & Ops step named "Execute Action" returns error Bad Gateway on "name of action" dropdown

MrMJFisher 46 Reputation points
2024-02-27T01:31:04.7866667+00:00

Logic App's step was working last Friday (2024-02-23) and at about 11:44 am PST it stopped working today (2024-02-26). The step was using the Fin & Ops (Dynamics 365) API connection using a service principal and secret. None of the service principal's secrets have expired. Microsoft 365 and Azure health pages do not show any relevant outages or issues. The step is called "Execute an Action". The instance drop down pre-populates with all instances. I selecting our development (sandbox) instance. The next dropdown is named "Action" or "Name of action" when it tries to populate the dropdown box returns the following error:

Could not retrieve values, BadGateway More diagnostic information: x-ms-client-request-id is 'AFA7A71F-C3E0- 4F80-9F3D-2F3D1CF871FB'.

User's image

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,082 questions
{count} votes

1 answer

Sort by: Most helpful
  1. MrMJFisher 46 Reputation points
    2024-02-27T21:19:12.7166667+00:00

    We suspect it was a change made where we defined an optional parameter in the AX method that implements the oData action; thus, when calling it through oData we got a message mentioning "Ambiguous match found." https://daxonline.org/1582-odata-actions.html


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.