Hi there @gj0. Sorry we seemed to have missed this post. Did you manage to get around the error? Someone has already looked into solving a similar error here.