Fixing “Flow Client Error: BadRequest” in Power Automate Unbound Actions

In this blog, we’ll cover why the “Flow Client Error: BadRequest” error while working with Power Automate occurs and guide you through the exact steps to resolve it, ensuring your flows run smoothly without unnecessary disruptions.

Have you ever come across this error? It can be frustrating, especially when the error message doesn’t provide much clarity. If you’ve faced this issue while using the Perform Unbound Action step, don’t worry, you’re not alone.

Let’s Understand the Problem First

When activating a flow that includes the Perform Unbound Action step, you might receive the following error:

This error can be difficult to diagnose since it doesn’t explicitly point to the issue. To troubleshoot, you should check multiple factors:

• Review the business logic in your custom action’s C# code.
• Verify that all parameters are correctly passed.
• Reconfigure connection references and ensure all connectors are active.
• Check the flow owner’s security roles and confirm an active Power Automate license.

If the error persists despite these checks, the issue is likely that the custom process (Action) used in the “Perform Unbound Action” step is turned off. Since Power Automate relies on this action’s metadata, the flow fails because it’s trying to call a process that isn’t available.

Solution: To fix this error, you need to activate the custom action. Once enabled, the error should disappear immediately. This highlights the importance of ensuring all referenced components in your flow are properly configured and active.

Steps to Fix the Error

1. Ensure the Custom Action is Enabled

• Navigate to Power Apps → Solutions.
• Locate the custom action (find in Processes) referenced in the Unbound Action step.
• Ensure that the process is enabled.

Before clicking “Turn on”:

After clicking “Turn On”:

2. Ensure the Connection reference is correctly configured and Active

3. Refresh the Flow and Activate Again

• Return to Power Automate.
• Open the flow and refresh.
• Save and click on the Turn on Button.

4. Validate the Action Name and Input Parameters

• Ensure that the exact name of the custom action is correctly referenced.
• Verify that all required input parameters are properly defined.

Conclusion

When using Unbound Actions in Power Automate, remember to:

• Check the connection reference before enabling it.
• Keep the custom action (process) enabled.
• Pass the correct input parameters.

By following these steps, you can avoid this error and ensure your Power Automate flows run smoothly!

Drop a comment if you’ve faced similar issues or need further assistance!

The post Fixing “Flow Client Error: BadRequest” in Power Automate Unbound Actions first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Original Post https://www.inogic.com/blog/2025/03/fixing-flow-client-error-badrequest-in-power-automate-unbound-actions/