Hey @Fl4m3Ph03n1x, did you ever figure this out? What was it?
Yes, we figured. Turns out it was the issue described by @chasers. I was quite hard to find.
