I think it was the double Veo3 that blocked it. My bad!

I'd be surprised if that was it... we gotta do a better job surfacing the errors and we will