Let's suppose to have:
- resource R1 supporting user propagation
- group G with resource R1 assigned
- resource R2 supporting user pull
- pull task T for R2, with user template set for granting G membership
When executing T the first time, user U is created internally and propagated to R1, as expected.
If U is modified on R2 (attribute change), when T is executed again the expected change is reflected on U internally. Nothing is changed, however, on R1.
If U is modified on R2 again and T executed the third time, the expected change is still reflected on U internally. R1, however, receives the change coming from the former T execution.