@Aleksi_Alkio I read the article and from what I understand I should add a column that verifies that the data was already updated, but, since the workflow rule is executed before the data is available, that only makes it false and does not run. As a consequence, it occurred to me to change the focus of the problem and instead of assigning the mother table to the workflow, I assigned it directly to the daughter table, assuming that in that way the workflow would only be executed after updating that table (which is the one that it has the data that interests me), and I was surprised that it was executed again before the table was updated. That is, after updating the mother table, but before the daughter. Why does this happen?
Can a delay be applied for the workflow rule to be executed a few minutes later?
Or is it that I did not understand the article?