Action invalid – The action has invalid configurations or parameters.

When working with Power Automate, you might encounter the following error:

“Action Invalid – The action has invalid configurations or parameters.”

This error occurs when an action in the flow is improperly configured, has missing or incorrect parameters, or does not meet the requirements of the connected service.

---

2. Causes of “Action Invalid” Error

Several factors can lead to this error in Power Automate:

1. Missing Required Parameters – Essential fields in the action are empty or incorrect.
2. Incorrect Data Type – The input value does not match the expected data type (e.g., text instead of a number).
3. Mismatched Schema in JSON Payloads – The JSON structure does not align with the expected format.
4. Expression Errors in Dynamic Content – A formula or expression used in an action is incorrect.
5. Invalid API Request Format – If calling an API, the request structure may be invalid.
6. Unsupported Functionality in the Selected Connector – Some actions require a specific Power Automate plan.
7. Outdated or Deprecated Action – The selected action is no longer supported by Microsoft or a third-party service.
8. Invalid Connection Reference – The action refers to an outdated or deleted connection.
9. Incorrect URL or Authentication in HTTP Requests – If using an HTTP action, the URL or authentication method may be incorrect.

---

3. Step-by-Step Troubleshooting Guide

Step 1: Identify the Invalid Action

1. Open Power Automate (https://flow.microsoft.com).
2. Navigate to My Flows and select the affected flow.
3. Click Run History and locate the failed run.
4. Expand the failed action to review the detailed error message.

Solution:

• Look for error details indicating missing fields, incorrect data types, or configuration issues.

---

Step 2: Check Required Parameters

Many actions require mandatory fields that must be correctly filled.

Solution:

1. Open the flow in Edit Mode.
2. Review the action settings and ensure all required fields are populated.
3. If using dynamic content, verify that the expected values exist in previous steps.
4. Click Save and Test the flow.

Example:

• In a “Create Item” action for SharePoint, missing a required field like Title will cause an error.

---

Step 3: Verify Data Types

Power Automate expects specific data types for each field (e.g., text, number, boolean).

Solution:

• Open the action and check the expected data type (e.g., string, integer).
• Use the “Convert” function in expressions to transform values if needed.

Example:

• If a field expects a number but receives text, use: int(variables('YourVariable'))
• If a boolean field expects “true” or “false”, ensure values are properly formatted.

---

Step 4: Fix JSON Payload Issues (For API Calls)

If the action involves JSON payloads, an incorrect schema can trigger the error.

Solution:

1. Validate JSON formatting using an online tool like https://jsonlint.com.
2. Ensure the expected keys match the required format.
3. If the schema is autogenerated, regenerate it to match the latest format.

Example:

• A missing required property in a Dataverse API request could cause an invalid action.

---

Step 5: Correct Expression Errors in Dynamic Content

Expressions in Power Automate must follow the correct syntax.

Solution:

1. Open the action and check any expressions used.
2. Ensure the formula follows Power Automate expression syntax.
3. Remove and re-add dynamic content if it’s showing errors.

Example:

• Incorrect: adddays(‘2025-03-01’, 5) // Wrong single quotes
• Correct: addDays('2025-03-01', 5) // Proper single quotes

---

Step 6: Ensure the Action Supports the Used Connector

Some actions are limited to specific Power Automate plans or licensing tiers.

Solution:

1. Check Microsoft’s official documentation for the action.
2. Upgrade to a Power Automate premium plan if required.

Example:

• The “HTTP with Azure AD” action requires a premium license.

---

Step 7: Verify Connection References

An action may fail if it references a deleted or incorrect connection.

Solution:

1. Go to Power Automate > Connections.
2. Check for broken or missing connections.
3. Re-authenticate or create a new connection and update the flow.

Example:

• If a SharePoint action references an expired connection, reconnect it.

---

Step 8: Check for Deprecated Actions

Microsoft occasionally removes or updates actions in Power Automate.

Solution:

1. Check Microsoft’s Power Automate updates to see if an action is deprecated.
2. Replace old actions with their latest equivalents.

Example:

• The “Office 365 Outlook” connector has updated email actions; older ones may stop working.

---

Step 9: Validate HTTP Requests (For Custom APIs)

If using an HTTP action, the request may be invalid.

Solution:

• Ensure the URL is correct.
• Verify the authentication method (e.g., OAuth, API key).
• Check if the API requires additional headers.

Example:

• If calling a third-party API, ensure that the authorization token is included in the request headers.

---

Step 10: Rebuild the Action

If an action remains invalid despite troubleshooting, try recreating it from scratch.

Solution:

1. Delete the invalid action.
2. Add a new instance of the same action.
3. Reconfigure all required fields.
4. Save and test the flow.

Example:

• If a “Send an Email” action is invalid, delete and add a new Outlook action.