# Sequence of Actions **URL:** \ **Category:** General Q&A\ **Created:** [September 23, 2026, 2:27pm UTC](https://community.easymorph.com/t/sequence-of-actions/6797 "2026-09-23T14:27:22Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![roberto](https://community.easymorph.com/user_avatar/community.easymorph.com/roberto/32/8595_2.png) [@roberto](https://community.easymorph.com/u/roberto)\ **Post date:** [September 23, 2026, 4:10pm UTC](https://community.easymorph.com/t/sequence-of-actions/6797/4 "2026-09-23T16:10:12Z")
Hello again! Just wanted to add that derived tables are executed sequentially - the source table is executed first, and afterwards the derived table. You will find a useful diagram in this thread: [Understanding derived table execution sequence](https://community.easymorph.com/t/understanding-derived-table-execution-sequence/4210/2). In the case you have a complex workflow with many tables and sequence actions, you can also split whole groups of tables into modules. So you run certain actions, and afterwards you call a certain module, that contains all the sequence of actions that need to take place afterwards. It's a way to simplify execution order management when there's many tables to take care of. More information on modules: [Calling modules/projects (subroutines)](https://easymorph.com/learn/subprojects). --- _[View the full topic](https://community.easymorph.com/t/sequence-of-actions/6797)._