Unanswered

Chatbot - Posting a Chat Message on Teams - Bad Gateway

(0) Share

Report

Posted on by Hank123

Hello guys! I cant figure this out, really need some help.

Trying to make an "auto-reminder" ChatBot with Power Virtual Agents as part of a Flow, once the Flow triggers, the Chatbot should be sending an auto message in a chat on Teams. However, once I test the Flow it keeps running and running and never sends the message on Teams.

When I click the "View" button on retries, it says:

What its really baffling though is that this is a Chatbot tested from the Unified Canvas (preview) option, not the Build for Production one. I tested the same Flow as described above and it worked fine, its only happeining with the Unified Canvas (preview).

Also, (not sure if it matters) I am testing with my email address, the email address for the environment and the email address for testing are the exact same.

Any help would be so greatly appreciated, thanks!

Categories:

Business Process Flows

I have the same question (0)

All responses (4)

Answers (0)

JamesDix_n 203 on at

Like (0)

Report

Re: Chatbot - Posting a Chat Message on Teams - Bad Gateway

Hi Hank123, welcome to the Power Automate Community - hopefully we can resolve this. I have a similar flow set-up but we use the Flow Bot instead of a virtual agent. This seems to generate fewer parameters and I wonder if that's where your error is occurring? It's an option in the 'Post as' dropdown list.

For example, these are the parameters the Flowbot generates for the input (I've added the square brackets.)

"parameters": {
"poster": "Flow bot",
"location": "Group chat",
"body/recipient": [CHATID]
"body/messageBody": [MESSAGE].

It also looks like you could be requesting the flow send a teams message to your email which wouldn't work. Make sure you identify the correct teams channel to post in, obtaining the Teams channel/chat id if necessary.

Thanks,
James

Was this reply helpful? Yes No
Hank123 8 on at

Like (0)

Report

Re: Chatbot - Posting a Chat Message on Teams - Bad Gateway

Hi @JamesDix_n !

Thank you so much for your reply.

Now, yeah, indeed I do have the option to set Flow Bot as the one sending messages but Virtual Agents Chatbot is like my end goal of having a more custom bot for daily tasks. If there only was a way to customize Flow Bots name and chat icon on Teams I wouldn't use Virtual Agents one ha.

Now, directly to the technicals, Virtual Agents Chatbot has two options to create a new bot:

What is really baffling is that the above flow for automated messages on Teams works fine with the "Build for production" bots, but the Topic variables are not editable and I need the bot to have a certain customized limited funcionality to achieve my end goal (very in my job specific goal).

The problem described in my OP seems to only happen with unified canvas preview, which is the actual bot that can be fully customized... (I am not sure if its because of the preview state or has limited funcionality in free plan.. just don't know).

Also, the built for prod bot sends messages to my Teams fine (I'm doing this sending messages to myself for testing purposes only) but it is the unified canvas one that throws the bad gateway error (yes I do have it installed on Teams and published and everything).

Was this reply helpful? Yes No
JamesDix_n 203 on at

Like (0)

Report

Re: Chatbot - Posting a Chat Message on Teams - Bad Gateway

Hi Hank,

That is bit of a conundrum. You can set the Flow Bot to post as you, would that work?

What do you need your bot to do in terms of the customised limited functionality? I wonder if there's any other Power Automate functionality that you might be able to use to achieve these aims?

As you said, it might be something to do with the functionality of the free plan but that's a tricky one to diagnose and a bit out of my skillset, I'm afraid.

Was this reply helpful? Yes No
Hank123 8 on at

Like (0)

Report

Re: Chatbot - Posting a Chat Message on Teams - Bad Gateway

Thanks @JamesDix_n !

Yeah, the usefulness of the virtual assistant bot is that you can pretty much customize it to your liking, including the name and icon that will show the end-user. My problem with Flowbot is that despite the fact that the actual message sent is "Flowbot sent you a message on behalf of Hank" it could also be a bit impersonal to the end-user (specifically for my job in project management).

But due to the lack of funcionality or really that I cannot understand the Bad Gatway error I think II'll just use Flowbot and be done with it ha. Hopefully when it is out of "preview" it works as inteded.

Thank you!

Was this reply helpful? Yes No