Unanswered

Power Automate Re-Triggering the Output even after condition is met once

(0) Share

Report

Posted on by AnandSkumar

Hi,

I have a power Automate flow to Trigger an email whenever a file is updated in Sharepoint. The Power automate flow is triggering when the file refreshes, but the flow runs again after 5 Minutes and trigger a secondary email even though the file in Sharepoint was not refreshed.

Please share some suggestions

Categories:

General topics

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Gdarmon Outlook 372 on at

Like (0)

Report
Copy link

Link copied!

Hi,
what SP trigger are you using ?
try to look into the file history .

Was this reply helpful? Yes No
AnandSkumar 8 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Using the SP Trigger of when the file gets updated. The file is Updated once in a Day by Python Script. But Power Automate Flow runs 2nd time exactly after 5 Minutes without any changes to the SP file.

Was this reply helpful? Yes No
Gdarmon Outlook 372 on at

Like (0)

Report
Copy link

Link copied!
Hi,
The behavior you're describing in Power Automate could be due to several reasons. Here are a few things to consider and troubleshoot:
Check Trigger Configuration: Review the trigger configuration in your Power Automate flow. Ensure that the trigger settings are correctly configured to monitor changes in the SharePoint file. For instance, ensure that the trigger is set to detect modifications and not just file creation.
Timestamp or Metadata Changes: Even if the file content remains unchanged, metadata changes (such as timestamps, permissions, or other file properties) might trigger the flow. Verify if any metadata or timestamp changes are causing the trigger to fire, even if the file content remains the same.
Check Python Script Updates: Although you mentioned the file is updated once a day by a Python script, double-check the script's behavior. Ensure that the script isn't inadvertently making modifications or updating file metadata in a way that triggers the Power Automate flow more frequently.
Concurrency Control: If your flow interacts with the file or SharePoint in a way that might trigger it again unintentionally (e.g., updating metadata or properties), consider implementing concurrency control or a delay action within the flow to prevent re-triggering immediately after the initial run.
Logging and Debugging: Implement logging or debugging within your flow to capture details about when and why it's triggering multiple times. This can help in identifying the specific conditions or actions causing the unexpected behavior.
Flow History: Check the Flow run history in Power Automate. It might provide more insights into the trigger conditions and execution, including any errors or additional information that could help diagnose the issue.
Gill

Was this reply helpful? Yes No
AnandSkumar 8 on at

Like (0)

Report
Copy link

Link copied!
Hi, I checked on the file in Share-Point and there are no Properties or Metadata level changes. I even created a parallel flow to trigger an email whenever there is change in properties of file but it is triggered only once when the file is updated.

Logging and Debugging: Implement logging or debugging within your flow to capture details about when and why it's triggering multiple times. This can help in identifying the specific conditions or actions causing the unexpected behavior. : How to activate this for a flow?

The Second Trigger always happen after 5-6 Min and it runs for ms. But this do trigger secondary email with same dataset

Was this reply helpful? Yes No
Gdarmon Outlook 372 on at

Like (0)

Report
Copy link

Link copied!

Hi,
Can you share the output of the two flows trigger action?
Is there a version control on the file ?

1. Enable Debug Mode
To enable debug mode in Power Automate Flow, follow these steps:
In the Flow designer, click on the “…” (ellipsis) button in the toolbar.
Select “Settings” from the dropdown menu.
Toggle the “Debug” switch to the “On” position.
Save your flow.
Now you can run your flow in debug mode by clicking the “Test” button and selecting “Test (debug mode)”.
Pro-tip: While debugging, make use of the “Inspect” feature to view the inputs and outputs of each action, making it easier to identify and resolve any issues.
2. Add a Debug Action
To add a debug action in Power Automate Flow, follow these steps:
Open your Flow in the Power Automate designer.
Select the desired action or step where you would like to add the debug action.
Click on the “Add an action” button.
In the search bar, type “debug” and select the “Add a debug action” option.
Configure the debug action by setting the necessary inputs or variables.
Save and test your Flow to trigger the debug action.
Check the debug output and logs to analyze the data and identify any issues or errors.
By adding a debug action, you can gain insights into the execution of your Flow, monitor the values of variables, and troubleshoot any problems that may occur during its execution.
3. Use the Run History
Using the run history in Power Automate Flow is a valuable tool for debugging and troubleshooting. Here are the steps to effectively utilize the run history:
Open Power Automate and navigate to the flow you want to debug.
Select the “Run history” tab to view a list of previous flow runs.
Click on a specific run to access detailed information, including input and output data for each step.
Review the run history to identify any errors or unexpected behavior.
Use the information from the run history to help diagnose and fix issues in your flow.
True story: During a recent project, I encountered an issue with a Power Automate Flow. By using the run history, I was able to pinpoint the exact step where the error occurred and quickly resolve it. This saved me valuable time and ensured that the flow ran smoothly without any further issues.
3. Use the Run History

Gill

Was this reply helpful? Yes No
AnandSkumar 8 on at

Like (0)

Report
Copy link

Link copied!

Hi,

I am unable to find any Debug Mode. Nor could find any issue in Run History. I created another flow and used the same trigger for Modification of File in Onedrive for Business. And still the same issue. Without any changes to the file in Onedrive, Power Automate is Triggering twice the flow.

Was this reply helpful? Yes No
AnandSkumar 8 on at

Like (0)

Report
Copy link

Link copied!

I am attaching the Raw data of Output for the Trigger When the File is Modified. Only Difference I could see is on the timing part. Any Idea why it gets triggered again?

Was this reply helpful? Yes No