Power Automate

Word Online (Business) action issue

(2) Share

Report

Posted on by A_Dean

I am receiving a status code 502 - Bad Gateway when using the action 'Convert Word Document to PDF'.

Is anyone else experiencing this issue?

"innerError": {

"status": 502,

"message": "There was a problem connecting to Graph API. Please try again.\r\nclientRequestId: 8eeb1b21-a433-4391-a410-4b4f1dd82922",

"error": {

"message": "There was a problem connecting to Graph API. Please try again."

"source": "wordonlinebusiness-we.azconn-we-002.p.azurewebsites.net"

}

Is there any way we can check the health of this Graph API?

Categories:

Using connectors

I have the same question (4)

All responses (3)

Answers (0)

Gdarmon Outlook 372 on at

Like (0)

Report

Hi,
To check the health of the Graph API, you can try the following steps:
Check the Microsoft 365 Service health dashboard to see if there are any known issues with the Graph API.
Try accessing the Graph API directly using a tool such as Postman or Graph Explorer to see
if you are able to connect to the API and retrieve data .
Br,
Gill

Was this reply helpful? Yes No
saggerfi 3 on at

Like (0)

Report

Hi guys!

I'm experiencing the same issue. In my flow, I use the "Convert Word Document to PDF" action, but only in one branch do I get a Bad Gateway message:

```

"status": 502,

"message": "There was a problem connecting to the Graph API. Please try again."

```

Was this reply helpful? Yes No
Suggested answer

SW-13110006-0 2 on at

Like (0)

Report
I have had this issue for over 2 weeks and I just solved it by clearing out my broswer cache. The Word to PDF function is now working again. Below is the advice Microsoft gave me. Suggestion 1 was the winning ticket.

Error 502 is an HTTP status code that indicates that one server on the internet received an invalid response from another server. This error is usually caused by two different internet servers that are having trouble communicating. It can occur due to a problem with your browser, an issue with your networking equipment, or some other in-your-control reason.

To fix this error generically, you can try the following:

Clear your cache and cookies

Disable your browser extensions

Switch your DNS server

If none of these solutions work, according to community contribution below, try accessing the Graph API directly using a tool such as Postman or Graph Explorer to see if you are able to connect to the API and retrieve data

Was this reply helpful? Yes No