I identified and resolved the issue.
In the nanoflow which was being applied there was a retrieval of an entity that was not in the Native configuration synchronization yet.
As a result, introducing this entity within the frame of reference of the Native app a rule must have been introduced in the background that caused all of the entity’s objects to be synchronized (or at least the synchronization was attempted).
Once I removed this entity from the nanoflow the issue was resolved and the Native app ran well.
Note: Despite the entity was being used in the Native app (within a nanoflow), no entry was added to the synchronization configuration setup.