How can I stop VERY quick subsequent runs of automation? UPDATED WITH SCREENSHOTS

[Kim Barry]

Multiple fields updates (preformed by other automations) can trigger this automation, and when all the fields are filled out, the automation conditions are met and trigger succeeds. Occasionally, this automation is triggered twice in quick succession. To address this, I implemented a process where the automation promptly updates a specific field and added a condition to the rule requiring that the field not contain this. However, because the triggers occur only 0.1 seconds apart, the subsequent execution does not detect the update. Any suggestions to prevent this? I believe the problem is with the trigger, because the previous automations occasionally end at the exact same time. The previous automations are triggered by a form being submitted. 

Trigger and trigger conditions

Updating the Description audit log and determining which field updates cause the problem

Attempted to add a check with the last update, this caused the automation to just not complete in these instances

The rest of the rule

[John Funk]

Hi Kim,

Please post a copy of your rule whenever you have a question about an automation. 

In this case, if I am understanding correctly without being able to see the rule, try adding a Re-fetch action immediately after the trigger (which I assume is a Field Value Changed trigger). Then be sure there is a check/Condition making sure that at least one of the fields is empty. 

[Kim Barry]

There is already a condition saying that none of the fields can be empty before it can continue.

[Kim Barry]

@John Funk I believe I have added the relevant information.

[John Funk]

Well, a picture is worth a thousand words as they say. And you have had two people request you add the screenshots. If you want help, you need to cooperate a little. We are volunteers here and just helping out in our "spare time". 

Sometimes there are typos in what has been setup that is more easily visible with the screenshot. And to see the flow as things are set up. There's nothing more we can do at this point. 

[Kim Barry]

@John Funk I added screenshots with the info. All I was saying was that I updated the post.

[John Funk]

My apologies for the misunderstanding! And thanks for adding those!

Okay, this might be as simple as adding a Re-fetch action right after the trigger. Or even a Delay action, maybe for 3-5 seconds, but let's see if the Re-fetch does the trick. 

The 2 causing the problem most often are probably Paragraph type fields which are bigger and got more going on with them. But, again, hopefully the Re-fetch works. 

[Marc - Devoteam]

Hi @Kim Barry 

Whenever you ask for help with an Automation Rule it will help us to help you if you provide:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

These questions are not for not willing to help, but to have community members understand on how automation works.

[Kim Barry]

@Marc - Devoteam I believe I have updated to add all the relevant information

[Marc - Devoteam]

Hi @Kim Barry 

Just as @John Funk suggested, I would have given you the same options, for a re-fetch or adding a delay.