Hi @JWebb,
We are currently working on fixing this issue, in the meantime take a look at this workaround:
best, Gabriel