LlamaParse closes connection unexpectedly

[majdalsado]

Describe the bug
We've noticed that LlamaParse can occassionally return an error unable to perform operation on <TCPTransport closed=True reading=False 0x7f57480c0a40>; the handler is closed
and fail when trying to use it to parse a pdf file via the python library.

It seems to happen immediately when we make a request but goes away if we retry at least once so it feels like a network connectivity issue.

Anecdotally I've noticed it happens more often on larger files rather than smaller ones.

Files
Random files, no pattern or specific trigger.

Job ID
When this bug happens no Job ID gets created, the error seems to happen before it does so.

Client:

• Python Library

Additional context
I call LlamaParse via LlamaParse.load_data(file_bytes). I'm not sure if the passing of file_bytes has something to do with it.

Here are logs of it happening whereby my function retries and it then goes through.

Job ID of the job succeeding it: a387462e-9c4a-467e-8330-c80a76c7f6cc

App that we're running is a Python FastAPI running on Railway with Uvicorn v0.34 (latest).