Hi @albanD,
That ended up letting me find the issue — initially it hadn’t seemed useful because the offending code was automatically generated and wasn’t available for the traceback. Temporarily changing that made it possible to see which line was responsible and resolve the issue.
(For us, it was an issue with how we had expressed a broadcasting operation.)
Thanks!