# Need an Action to force “Execute/commit previous Actions before continuing”

**URL:** <https://community.fibery.io/t/need-an-action-to-force-execute-commit-previous-actions-before-continuing/3083>\
**Category:** Ideas & Features\
**Tags:** automations\
**Created:** [July 19, 2022, 1:52pm UTC](https://community.fibery.io/t/need-an-action-to-force-execute-commit-previous-actions-before-continuing/3083 "2022-07-19T13:52:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [July 19, 2022, 1:52pm UTC](https://community.fibery.io/t/need-an-action-to-force-execute-commit-previous-actions-before-continuing/3083/1 "2022-07-19T13:52:08Z")

</div>

I’ve run into a couple situations where it would be very helpful if an Action was able to reference the results of previous Actions in the Rule (and/or in very-recently-executed Rules, which apparently don’t get immediately committed).

The simplest solution would seem to be an Action to force all the “pending” Actions to be executed/committed before continuing.

> [@What am I doing wrong?](https://community.fibery.io/t/what-am-i-doing-wrong/3080/4):
>
> Apparently it’s worse than that… It appears that additionally, the results of “very recently run” Rules (i.e., those triggered “at the same time”) are also unavailable slightly_frowning_face This is making it very difficult to do the following via no-code: Create a Button for the “Page” DB that creates and links five “Task” entities. Use a “Task” Rule to set the Start Date of each newly-created Task to the “most recently created Task’s” Due Date, plus 7 days (that bit is always empty). I’…

---

<div class="post-metadata">

**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\
**Post date:** [July 22, 2022, 8:42pm UTC](https://community.fibery.io/t/need-an-action-to-force-execute-commit-previous-actions-before-continuing/3083/2 "2022-07-22T20:42:25Z")

</div>

Hi, Matt!  
Noted, have that planned for some day in our backlog 💪

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [July 3, 2023, 4:09pm UTC](https://community.fibery.io/t/need-an-action-to-force-execute-commit-previous-actions-before-continuing/3083/3 "2023-07-03T16:09:46Z")

</div>

> [@Matt\_Blais](#):
>
> very-recently-executed Rules, which apparently don’t get immediately committed

AFAIK an automation that is triggered will execute all its actions in sequence. The changes in the first action step of a given rule should always be completed before the second step is started, and so on.  
However, formula fields are calculated asynchronously, so it is possible that a change in an automation step can cause formula recalculations which do not resolve before the subsequent automation actions.