cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jonathan42no
Frequent Visitor

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"}}'.

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! err1.jpgerr2.jpgss1.jpg 

1 ACCEPTED SOLUTION

Accepted Solutions
Vivabot
Frequent Visitor

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.

View solution in original post

9 REPLIES 9
SwapShells
New Member

I got this too, using similarly.

Serintes
Frequent Visitor

im facing this issue as well

SwapShells
New Member

Its not Version related i think, Most likely VPN related

VladislavICL
Regular Visitor

We got this issue one hour ago on all flows

SwapShells
New Member

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.

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

Serintes
Frequent Visitor

its working again Thank you

 

jonathan42no
Frequent Visitor

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

Vivabot
Frequent Visitor

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.

Helpful resources

Users online (4,151)