Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update triggers-troubleshoot.md #1439

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+9 −1
Open

Update triggers-troubleshoot.md #1439

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion articles/triggers-troubleshoot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,6 +208,14 @@ An example of idempotency would be checking to see if a duplicate SharePoint doc

Another possibility is for flow triggering multiple times might be having copies of the flow active in different environments that are triggering based on same condition. Use trigger conditions to customize triggers to reduce the number of times it triggers.

## My flow triggers unexpectantly

If you have your flow set to trigger when a Dataverse field is "Modified", you might see your flow run when you don't expect it. This is because "modified" in this instance means that the Dataverse field was "written to", even if the value is the same.

For instance, if the value of a field is "5", and another process (flow, plugin, etc.) also writes the value "5" to the field, that will trigger the flow. This can be difficult to determine sometimes, even if you have auditing turned on for that field. Auditing will only record when the value *changes*. So if the value that was written to the Dataverse field is the same, there will be no audit log showing a change, but your flow will trigger because the field was written to.

To help find what wrote to that field, take a look and see what other flows or processes were running at the time the flow was triggered unexpectantly.

## My recurrence trigger runs ahead of schedule

Confirm that you've set the **Start time** on the **Recurrence** card to ensure it runs only at the time that you need. For example, set **Start time** to '2022-10-10T10:00:00Z' to start your trigger at 10:00 AM.
Expand Down Expand Up @@ -288,4 +296,4 @@ You can try one of the following:

To resolve this issue, edit each flow and save it. The triggers should start firing again.

[!INCLUDE[footer-include](includes/footer-banner.md)]
[!INCLUDE[footer-include](includes/footer-banner.md)]