A question about action order in a workflow

We need to run three clone actions in a workflow in order to keep backups for different purposes and with different retentions. I tried to sequence the actions one after another

              [backup] ==> [clone1] ==> [clone2] ==> [clone3]

We found that if the clone action [clone1] skipped due to its scheduler, the actions [clone2] and [clone3] would not be run. Is this the normal behavior?

This is not what we want, each clone action has its own different scheduler. They should run on their scheduled dates regardless the result of other clone actions.

So we tried a different order

                                 |==> [clone1]

              [backup] ==|==> [clone2]

                                 |==> [clone3]

It works. The three clone actions will start at the same time after the backup succeed. Does this ordering have any performance concern as they run together?