Request to the Bot framework failed with error: '{"error":{"code":"BadArgument","message":"Incoming request was redirected to the wrong geo! Current geo: EUDB, Target geo: EMEA"}}'.

(3) Share

Report

Posted on by Community Power Pla...

Hello Team,

I have a these flows that gets the subject line of a particular email message and posts it in a teams group chat

basically:

"When an email arrives" ---> "Post a message in a chat or channel"

however, today the flow did not run per usual and got an error message:

"Request to the Bot framework failed with error: '{"error":{"code":"BadArgument","message":"Incoming request was redirected to the wrong geo! Current geo: EUDB, Target geo: EMEA"}}'."

has anyone encountered the same issue? can't find any solution right now. please help!

Categories:

General topics

I have the same question (0)

All responses (9)

Answers (1)

SwapShells 12 on at

Like (1)

Report

I got this too, using similarly.

Was this reply helpful? Yes No
Serintes 17 on at

Like (0)

Report

im facing this issue as well

Was this reply helpful? Yes No
SwapShells 12 on at

Like (0)

Report

Its not Version related i think, Most likely VPN related

Was this reply helpful? Yes No
VladislavICL 18 on at

Like (0)

Report

We got this issue one hour ago on all flows

Was this reply helpful? Yes No
SwapShells 12 on at

Like (1)

Report

There might have been a reroute due to failover at backend for MS. I Signed out and Signed back in and it seems to work fine for me now.

Was this reply helpful? Yes No
VladislavICL 18 on at

Like (0)

Report

Yes, it works! But I don't want to got this issue again)

Was this reply helpful? Yes No
Serintes 17 on at

Like (0)

Report

its working again Thank you

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

Like (0)

Report

The flows are now working again. relief! thanks for all you responses. hope this issue won't happen again

Was this reply helpful? Yes No
Verified answer

Vivabot 12 on at

Like (1)

Report

This was a Microsoft hiccup, it won't happen again, and if it does we can't do much about it.

It was 2-3 hours of failed flows with Teams connector everywhere... We are still finding and rerunning failed flows.

Was this reply helpful? Yes No