We experienced similar issue caused by many-to-many relationship.
The issue is fixed using the workaround to replace existing relationship:
{Source table}<Many-to-many | one direction>{Target Table}
with new relashiship:
{Source table}<Many-to-one | both direction>{intermediate table} <One-to-many | One direction>{Target Table}.
Detailed steps:
1. Create a intermediate table which has only one column. Column data is distinct values of many-to-many relationship column of source table.
2. Delete many-to-many relationship from source table to target table
3. Create many-to-one relationship from source table to intermediate table. Set relation filter to be both direction.
4. Create one-to-many relationship from intermediate table to target table. Set relation filter to be one direction.