We've fixed an issue affecting signals with the same name in different DDBs when those signals were routed to an external DataSource.
Previously, these signals could ultimately be written into OutsideWorldDDB, resulting in two identically named signals being placed in the same DDB and triggering a multiple producer conflict.
Signal handling has now been corrected so that signals originating from separate DDBs are handled appropriately when interfacing with external DataSources, avoiding these false producer conflicts.