504 Gateway Timeout on "When record created in Business Central" trigger

(2) Share

Report

Posted on by aorphan

160

Hello,

I have created a Flow (also tried with Logic App) with a "when record created in Business Central" trigger but I am constantly met with an HTTP 504 Gateway Timeout error when the trigger attempts to run. It ran just fine yesterday. What could be the issue, and what is the fix?

Thanks in advance!

Categories:

Using connectors

I have the same question (0)

All responses (14)

Answers (0)

Sort by

aorphan 160 on at

Like (0)

Report
Copy link

Link copied!

Full error here:
"error": {
"code": 504,
"source": "logic-apis-centralus.azure-apim.net",
"clientRequestId": "35252b79-2ba4-4a4a-8377-a2d8d50155e7",
"message": "BadGateway",
"innerError": {
"status": 504,
"message": "Request timed out.\r\n inner exception: A task was canceled.\r\nclientRequestId: 35252b79-2ba4-4a4a-8377-a2d8d50155e7",
"source": "dynamicssmbsaas-cus.azconn-cus.p.azurewebsites.net"
}
}

Was this reply helpful? Yes No
v-lin-msft 728 on at

Like (0)

Report
Copy link

Link copied!
Hi @aorphan ,

According to your descript about your problem, I can give you two suggestions as below,

Please update your connection or create a new connection and see if issue still exists.
Please check your subscription of Dynamic 365 Business Central whether expired.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
Rijk van Reenen 8 on at

Like (1)

Report
Copy link

Link copied!

Hi there,

I'm having the same problem; a few weeks ago it worked fine and all of the sudden it stopped working.

I've tried recreating the flows and checked the licenses and it's all ok.

When using a Business Central template approval flow that works; however triggering on a new record trows the 504 gateway timeout every time.

Was this reply helpful? Yes No
aorphan 160 on at

Like (0)

Report
Copy link

Link copied!

Hi @v-lin-msft,

It looks like another user has reported the same issue. Any chance your team can investigate?

Thanks

Was this reply helpful? Yes No
martinav 3,347 on at

Like (1)

Report
Copy link

Link copied!

All,

EVERY flow is experiencing very similar errors today. We have been having a teasing of issues since a week ago. Today, its completely wide spread and DEVESTATING. MS Ticket is in for the issue.

SR number 119043023002044

Was this reply helpful? Yes No
MaryMThompson 27 on at

Like (0)

Report
Copy link

Link copied!

Do you know if this issue is occuring again? I am having this same issue today.

Was this reply helpful? Yes No
Rijk van Reenen 8 on at

Like (1)

Report
Copy link

Link copied!

Hi,

I ended up contacting Microsoft and they helped me solve the problem in the back-end somewhere.

Regards,

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

@aorphan wrote:
Hello,

I have created a Flow (also tried with Logic App) with a "when record created in Business Central" trigger but I am constantly met with an HTTP 504 Gateway Timeout error when the trigger attempts to run. It ran just fine yesterday. What could be the issue, and what is the fix?

Thanks in advance!
@aorphan wrote:
Hello,

I have created a Flow (also tried with Logic App) with a "when record created in Business Central" trigger but I am constantly met with an HTTP 504 Gateway Timeout error when the trigger attempts to run. It ran just fine yesterday. What could be the issue, and what is the fix?

Thanks in advance!

Got the exact same experience. Any news on this? Can't find a solution anywhere.

Was this reply helpful? Yes No
aorphan 160 on at

Like (0)

Report
Copy link

Link copied!

No, it's still happening for us as well. No word from Microsoft on this. Probably due to the connector being in Preview state, but no word on when it goes live.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

OK. Well, I had a call with their support team last Friday. They couldn't fix it at that moment, and raised a high severity bug to their development team. They will keep me posted.

Was this reply helpful? Yes No