What is the order of actions? We have to import many tables and run actions on them. Some of these tables rely on other - we did find the synchronized action, but what about just for networking and latency issues? If we put the tables in their own groups and run all the actions, will the order of actions be left to right in the groups? I did have an issue when I moved my morph to the hub, it would not work properly when sending the files to a remote host so I put the tables into groups and it seemed to alleviate the issue. Many thanks as always
All the tables in a project module start executing in parallel, independently of the group in which the table is located.
If a table relies on another one (for example, having the "Merge another table" action) and the other table that has not yet been completely calculated, the merge action will only start executing when the other table is completely calculated.
The way to ensure that the tables are getting executed in the order you want (as there may be other dependencies that do not explicitly appear in the workflow), is to use the Synchronize action, as you mentioned.
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.
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).