Hello JoseMiguelPulgarin,
We have reviewed the behavior you described and can confirm that this is a known bug in the current implementation.
Unfortunately, at this time, we do not have a workaround available for this problem. However, we plan to fix it in the future.
As soon as the fix is ready, we will let you know.