Create Text With GPT - Manual approval action required now?

[CGX_bwang]

Hi,

We recently started running into an issue where the "Create text with GPT" action in Power Automate is requiring an approval action afterwards (each time the action is used) or it will give the error message below.  Previously, this was just a warning but now it appears to be mandatory and won't let you save the flow.  It also appears to be blocking previously built flows that used this action.  The error goes away if we add in the Start and wait for approval.  

Was wondering if anyone else has ran into this (or have any work-arounds) but for us requiring a manual approval each time the action is used would eliminate many of the use cases to automate certain tasks.

Thanks!

[Ashbhatia]

We appreciate and understand the concerns raised in this thread. Today, we published an article to raise awareness about the potential risks associated with generative AI when used in conjunction with automation, please take a read https://learn.microsoft.com/en-us/ai-builder/azure-openai-human-review. These emerging risks cannot be solely managed by the current content moderation systems. Hence, we're emphasizing the importance of human oversight in such scenarios, especially for unattended automation.

We acknowledge that there are many automation scenarios where the vulnerability and risks are low. In these cases, human review should ideally be avoidable. Rest assured; we are continually investing in enhancing the safety of our service as we move towards the general availability milestone.

Our commitment lies in empowering developers by giving them more control, while also guiding them on how to minimize these risks effectively. Thank you for your understanding and patience as we navigate this uncharted territory.

[ARB_wcc]

So, as we sail through this sea of uncharted territory, why not upgrade the ship a bit? Can't wait to set sail with 'Transform with GPT-4V(ision)' — it's gonna be the 'Love Boat' of AI connectors! 😁

P.S. If Microsoft decides to make this connector a reality, just know that I'm officially calling dibs on the name!

[bwtwma]

This was a stupid decision. The product manager behind this should be fired from Microsoft.

This can be circumvented using the OpenAI API directly. And two, assumes that there are no manual review processes OUTSIDE OF POWER AUTOMATE.

All this did was stop our ability to update power automate flows using this action as a company. As the CTO of an airline, I can't trust Microsoft with our no code/low code anymore if they continue to make such thoughtless decisions. I have escalated this to our CSM, corporate accounts I highly recommend you do the same.

[takolota]

At this point I would have saved several hours of my time if I just built the Azure OpenAI module for GPT & used the HTTP action to call it instead of dealing with this stupid requirement.
I had to update a flow in my solution to include the approval. I added the static result workaround. It then failed to trigger because of a connection issue with the Approvals action & gave a warning about it. So I manually ran the flow to make sure the connection was good. No more error message when I perform the action in my app that triggers it.
But then the flow just didn't trigger at all & didn't give any error message.
Microsoft let me bill you for the amount of stupid hours wasted on this.

Previous Error Messages:


What didn't work:
Creating a copy of the flow & using that in the app
Creating a new connection on the approval action
Refreshing the flows in the app

After 3.5 hours the only thing that did work:
Removing the flow from the app entirely & re-adding it (Why does this work but refreshing or creating an entirely new copy didn't? Who knows.)

[ARB_wcc]

I'm facing an issue with old flows that are operational but lack approval actions. Whenever I try to update these flows by incorporating the necessary approval steps, I continue to receive a warning message that prevents me from saving my changes. The issue here is that these aren't simple flows; they contain multiple branches and connections, making them time-consuming to rebuild from scratch. So instead of focusing on new flows, I find myself going back to revisit old flows more than I'd like to. That's also one of the reasons why I'm still online at 12 AM 😭

Microsoft should at least re-imburse the overtime to my employer lol 

[Rolson1]

Did they kill the static result workaround?  I ran my flow as suggested and it's still greyed out

[ARB_wcc]

If that happens it will render the connector useless, this connector is by far the most important connector in our flows now. 😅 

Everything seems normal in our environment 

[takolota]

@Rolson1 If it is not working for you, I had someone else mention to me that you could just set the timeout on the Approval action to like 1 second, then set the next action's run after settings to run on success or on timeout.

[ARB_wcc]

Tested and approved sir, always great to have more than one backup plan!

[gbego · Accepted solution]

Thank you all for your feedback on this topic. Update from the product team: We've reverted the human in the loop approval to a non-mandatory warning, after successfully testing out that the feature meets all of our latest Responsible AI guidelines. The fixes are rolling out today in the US, and tomorrow in EU.

We set a very high bar for Responsible AI at Microsoft, and the initial decision to force human in the loop approval was meant as a protective measure to force customers to always review AI-generated text before using it in a workflow. Now that the feature is Generally Available, we are making this step recommended but not mandatory, for you to choose. Thanks again for your feedback on this topic and looking forward to hearing about what you are building with GPT Prompts!

[ARB_wcc]

Are we supposed to create custom prompts now and then load the prompt with the "Create text with GPT using a prompt" connector? What happens with old flows that were using the preview connector, because they are still functional. 

[Antrod]

Hi @ARB_wcc ,

Indeed, flows using the old action are still functioning but note that this action is now deprecated and is not supported anymore. It's also possible that the action stops functioning in the coming months. We recommend that you replace any old GPT action with the new "Create text with GPT using a prompt" by copying the prompt instructions.

"Create text with GPT using a prompt" is now the official and supported way to use GPT in any environment (including production) with AI Builder & Power Automate. 

As mentioned by @gbego , this action doesn't require a mandatory human review step anymore and will benefit from many improvements in the future!

[ARB_wcc]

Thanks @Antrod, that's what I thought.

I was surprised to find out that my existing prompts in the old connector were not opening, marked by the "broken connection" plug icon in the flow as you can see below. Fortunately, I've maintained a backup of my prompts as txt files in SharePoint. And it looks like old prompt content is still accessible by examining the run history of a flow that has been executed recently, so just need to replace the connectors now 

[BTPM]

How do we prevent this happening again?

This wasn't responsible in itself to just roll something out like this. The people who were behind this are not the types of people I want in control of AI.

What organizational changes will be made as a result?

[ARB_wcc]

Well, unexpected changes like this were bound to happen. We were all just using a preview feature at our own risk. Hopefully now that it's GA it won't happen again. Hopefully 😓

[gbego]

Old flows with the preview connector should still work but we recommend that you migrate to using the new GA Connector for production workflows. When creating a new flow, only the GA Connector will be available. Once users have stopped using the preview connector we will gradually sunset to only support the GA Connector (timeline still TBD).

@ARB_wcc , @BTPM : would love to follow up privately to better understand the issue you are facing.

[gbego]

We are investigating this, more details to follow. In the interim, if you switch to the new Power Automate Designer, this issue shouldn't happen.

[ARB_wcc]

Can't use the new designer because my flows have "too many actions".