Google Calendar Connector error: "...'connectorplatform.powerplatform.com' could not be resolved."

(0) Share

Report

Posted on by JS-05081258-0

On July 29 my 2 Google Calndar Connector flows stopped triggering and the flow checker is showing the following error message: "The provided host name 'connectorplatform.powerplatform.com' could not be resolved." After some tinkering last night (8/4), I tried refreshing the OAuth connections to the Google account and was able to get the flow checker errors to go away temporarily. As of this morning, the flow checker errors are back and my flows are not triggering. I don't know why this started all of a sudden and the flow checker suggests that this is a temporary situation and a system problem but I cannot seem to find any reference to it or outages. If I do an NSlook up on that domain from my Mac, it comes back with: ** server can't find connectorplatform.powerplatform.com: NXDOMAIN". So it seems like there is some type of DNS issue upstream on the Microsoft side, but it seems unlikely that that would go unnoticed and unresolved for a week. Don't know where to go from here on this problem because the flows were working and nothing has changed other than apparently something on the platform.

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Mohsin Ali 655 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @JS-05081258-0 - Since the flows were previously working and refreshing the Google OAuth connection only resolved the issue temporarily, I would strongly recommend raising a Microsoft support ticket at this point.

The error appears to be occurring at the connector/platform level rather than within your flow logic. Microsoft Support should also be able to check the backend telemetry and determine why the Google Calendar connector is attempting to reach connectorplatform.powerplatform.com and why that operation is failing.

When opening the ticket, I would include the affected Flow IDs, Environment ID, approximate time when the issue started, and the complete error details. This should help Microsoft trace the corresponding backend requests.

If my suggestions are helping you to resolve the issue or giving clue to further investigate, then please mark it as Verified as shown below. This way you're also helping the community to quickly navigate the resolution.

Was this reply helpful? Yes No
Mohsin Ali 655 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @JS-05081258-0 - Just wanted to follow-up if the suggestions shared above really helped or pointed in right direct?

Was this reply helpful? Yes No