The below steps are to follow to see the behavior while migrating a resource by selecting 'Keep Non Colliding' as a retention policy:

1. Open the TDV Deployment Manager and create two sites (source and target).
2. Create a resource bundle with a sample resource. For e.g. Create a sample view 'view1' on top of any tables/views from the examples folder on the host.
3. Create a plan to migrate the resource from the source to the target and choose the retention policy as 'Keep Non-colliding'.
4. Execute the plan, the plan is executed successfully and the resource got migrated successfully.
5. Delete the migrated resource 'view1' from the target.
6. Execute the same plan again which is configured to migrate 'view1' from the source to the target.
7. The plan is executed successfully (could be seen as 'SUCCESSFUL' in the execution log), however, if the user checks the resource did not get migrated on the target side (can be confirmed using the Studio as well).

All supported environments

The above-mentioned behavior is because of the fact that the Deployment Manager only copies the resource to the target if it detects that the resource was changed at the source for instance if the user makes a minor edit to 'view1' on the source, and then execute the plan the second time as Incremental deployment is based on tracking changes on the source, not the target.

Below are steps that could be followed to get the resource migrated for subsequent executions:

(i) Follow the steps from (1) to (5) above unchanged.
(ii) Now modify the plan, i.e. any kind of minor edit so that the Deployment Manager thinks that the plan is a new one and not the same old plan. 
(iii) Now execute the plan again with the same retention policy and one can see the resource being migrated. (can be confirmed using the Studio as well).

However, if the user does not intend to make a minor change at the source, then the other way to resolve this is to use the retention policy as KEEP_NONE.

This article focuses on how the Deployment Manager behaves when the retention policy is selected as 'Keep Non-Colliding' while migrating a resource from a source to a target site. This article also mentions the plausible workaround for how to get it executed.