We have created three data pools in Datamaker (DataPool1, DataPool2, and DataPool3), and designed a Self-service Tile, taken from the ARD Flow, that references the three data pools in the sequence of DataPool1, DataPool2, and DataPool3.
When executing the publish job in TDM Portal, we see the data pools are getting executed in the wrong sequence: DataPool2, DataPool1, DataPool3
Release : 4.9.1
Component : Web Portal - Publishing
The "TDM Job Submission Order" is set in the Flow Properties - General Properties dialog, at the bottom of the screen, as shown below:
Looking at the copy of the ARD flow you provided, I see the "TDM Job Submission Order" has been configured as "Calculate Job Submission Order", which tells TDM to ignore the order set by the ARD Flow (VTF logic), and to calculate the order based on the tables "parent to child" relationships. TDM will execute the parent first and then the child, as a result, this could change the sequence order of execution to be different from what is defined in ARD.
It's recommended to set this back to the default setting: "Submit as Encountered in VTF Logic", and save to the TDM Repository, and see if this corrects the behavior you are seeing for the publish jobs.