This issue has been solved via the support channel.
For anyone experiencing something similar, see more information here: