# Understanding derived table execution sequence

**URL:** <https://community.easymorph.com/t/understanding-derived-table-execution-sequence/4210>\
**Category:** General Q&A\
**Created:** [January 11, 2023, 10:50pm UTC](https://community.easymorph.com/t/understanding-derived-table-execution-sequence/4210 "2023-01-11T22:50:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisllawson](https://community.easymorph.com/letter_avatar_proxy/v4/letter/c/a88e57/32.png) [@chrisllawson](https://community.easymorph.com/u/chrisllawson)\
**Post date:** [January 11, 2023, 10:50pm UTC](https://community.easymorph.com/t/understanding-derived-table-execution-sequence/4210/1 "2023-01-11T22:50:20Z")

</div>

I've read the tutorials several times and thought I understood but am perplexed by my workflow not working as anticipated.

Setting up a test use case, I anticipated the flow to execute as shown with the blue circles.

However, what really happens is the yellow triangle sequence.

What am I missing?

 ![execution sequence](https://community.easymorph.com/uploads/default/original/2X/c/ce846e340aae6748647d906f1d916ca3743871d9.jpeg)

---

<div class="post-metadata">

**Author:** ![dgudkov](https://community.easymorph.com/user_avatar/community.easymorph.com/dgudkov/32/5_2.png) [@dgudkov](https://community.easymorph.com/u/dgudkov)\
**Post date:** [January 11, 2023, 11:06pm UTC](https://community.easymorph.com/t/understanding-derived-table-execution-sequence/4210/2 "2023-01-11T23:06:32Z")

</div>

Once a workflow becomes non-linear, there is no determined sequence of execution. The basic principle is as follows:

 ![image](https://community.easymorph.com/uploads/default/original/2X/7/7fef44e91d297548e314048783124426800325f3.png)

In the image above, tables "Derived A" and "Derived B" will be executed simultaneously (i.e., in parallel). However, if the CPU has too few cores to support a high degree of parallelism, then they can be executed one after another, in any order - A-then-B, or B-then-A, depending on the availability of CPU cores.

All in all, you shouldn't worry about the execution order, EasyMorph takes care of it. If you need to enforce a specific order of execution of actions in _independent_ tables, use the ["Synchronize" action](https://help.easymorph.com/doku.php?id=transformations:synchronize).