We had another closer look at this, and found the cause. Actually the connection for the vectorizer to OpenAI took quite long during your import (>30s), probably because they were under heavy load. This caused
- Weaviate to take exceptionally long to import your objects
- The Python client to eventually time out
- The load balancer to assume that Weaviate was not available, resulting in the 502 code (this should only have lasted for a couple of seconds)
Unfortunately there’s nothing we can do about the external request timing out, this is a scenario that might occur and is out of our control. However we are already making plans to improve the communication and timeout processes around this behaviour on our side, so that you should be able to get better insights right from the responses in the future.