PL 400: Identify and resolve connector and API errors(Manage and troubleshoot apps)

Data works as fuel in the business world. Connector provides the bridge between data source and power apps and power platform. Connector is core component of power platform. A connector may provide table of data or action. A connector can provide a table of data or action. However, Microsoft offers over 300 different connectors, it also allows creating custom connectors for communication between different apps. All connectors sit on a hosting environment that is owned by Microsoft.

As we know a connector is a wrapper or proxy around an API that interacts between power automate or power apps and back end service or data source. It allows a bi-directional communication and can access data form both cloud and on premises servers.

Custom Connector Architecture:



We have already discuss design the custom connector. for the more update, please click this link. Here we will discuss about connector and API errors and their resolutions.

HttpRequest- Failure : Server returned: 500 Internal server Error:

HTTP status code 500 is a common error response, indicating that the server encountered an unexpected unexpected condition that prevented it from fulfilling the request.

Resolution:

There can be several reasons for what might be causing this issue, but the most common reason is related to how the path and host fields are defined in the swagger. The path of each action is relative to the host of the API you're trying to reach, which ends up getting constructed as <host/path>.


Service Timeout:

Service timeout is also a common error that occurs when the server takes so long to respond. Possible reasons could be server issues, outdated browser, cache, sporadic internet connection and others.

Resolution:

Generally we try to connect again the service.

InvokerConnectionOverrideFailed error:

If we get an error similar to '{"error":{"code":"InvokerConnectionOverrideFailed","message":"Could not find any valid connection for connection reference name 'shared_office365' in APIM tokens header."}}'. Try these:

Resolution:

  • Clear the browser's cache.
  • Delete the connection and then re-add it.


The reply url specified in the request does not match the reply urls configured for this application.

This is configuration issue when we create new custom connector

Resolution:

To resolve this error, we need to add Redirect URL generated by custom connector in App registration Reply URL’s.

Comments

Post a Comment

Popular posts from this blog

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Is Debt Prosperity or Trap?

Exam PL-400: Microsoft Power Platform Developer