No, each row edit represents a separate state of the row. That single row state should be compared against EACH workflow condition and then trigger each workflow separately. Even if the workflows run in series, any changes to the row state from the first should NOT affect the second. (NOTE: data from OTHER tables can change and cause an impact because they are usually retrieved from the table).
You may be uncovering a bug and it seems it may be related to how ChangeTimestamps are treated.
However, you can easily remedy your issue by combining the workflows together. If they have the same exact condition, there really is no need for them to be in two workflows. In fact, from an efficiency perspective I would suggest to combine them. Consider that the majority of your row changes probably DO NOT trigger either workflow. But each of those non-triggering changes still need to check the conditions. By combining them, you will cut those number of checks in half!
LinkedIn
Twitter
