MigrationTargetDocumentum appears to be eating a DM_SYSOBJECT_E_CANT_FETCH_ACL error in some environments.
A migration was run against the Astellas DEV environment with an invalid ACL domain value. No errors were thrown and the migration failed count was 0 when renditions were not attached. When renditions were attached, the error presented itself as a DM_SYSOBJECT_E_NO_NEW_ATOMIC error (better than no error, but super confusing to debug). Running the same configuration against the TSG DEV environment, the expected error was thrown. The differences between the two environments was not investigated.