Power Platform Community Forum Thread Details

Pretty experienced flow user here. I've run into an odd one... It's a new power platform environment for a customer. I have a very basic setup:

When a record is created in BC using v2.0 standard API on Customer Table

Then initialize a variable

The flow will not trigger. However, if I get records using the same API setup, no issues. Any ideas? It's not in a solution and is being triggered from the default environment.

Thanks!

Categories:

Building flows

Hi DB-17032133-0,

Thank you for choosing Microsoft Power Platform Community.

Check out these fixes:

1. Check Trigger Configuration

Ensure that the trigger is correctly configured for the creation of records in the Customer Table using the v2.0 API.

Verify that the API endpoint and authentication settings are accurate

2. Default Environment Limitations

The default environment may have restrictions or configurations that prevent certain triggers from firing. Consider moving the flow to a dedicated environment or solution to see if it resolves the issue.

3. Data Loss Prevention (DLP) Policies

Check if there are any DLP policies in place that might block the flow from triggering. These policies can restrict the use of certain connectors or APIs in the default environment.

4. Flow Registration
Sometimes, the flow's trigger might not be properly registered. Try the following steps:

Edit the flow and re-save it to force re-registration.

Temporarily change the trigger to another action, save the flow, and then revert it back to the original trigger.

5. Environment Administration Mode
If the environment is in Administration Mode, asynchronous processes like Power Automate flows may not run. Check the environment settings in the Power Platform Admin Center and disable Administration Mode if it's enabled.

6. API Permissions
Confirm that the API has the necessary permissions to trigger the flow. If the API is restricted or lacks proper access, the flow won't fire.

7. Test with a New Flow
Create a new flow with the same trigger and actions to rule out any issues with the existing flow configuration.

8. Monitor Flow Runs
Use the Flow Checker in Power Automate to identify any errors or warnings.

Check the flow's run history to see if there are any logs or errors when the trigger is supposed to fire.

If none of these steps resolve the issue, it might be worth reaching out to Microsoft Support for further assistance.

Happy to help,

Robu1 | Superuser & Moderator