Find answers from the community

Updated 6 months ago

Hi guys, using LlamaParse is suddenly

At a glance

A community member is experiencing issues with LlamaParse, where the process is taking longer than usual and they are receiving a "404 Not Found" error. Other community members suggest that this may be due to the user having enabled HTTP logs, which is expected behavior as the system waits for the processing to complete.

Useful resources

aaelita

Hi guys, using LlamaParse is suddenly taking a lot longer than it was before, and I'm now getting this error repeatedly before my document actually begins parsing: "HTTP Request: GET https://api.cloud.llamaindex.ai/api/parsing/job/206bca8a-b28c-4d35-a48e-91d4af8ba45d/result/text "HTTP/1.1 404 Not Found""

4 comments

LLogan M

cc @pld

LLogan M

the 404 is probably from enabling HTTP logs right? I think thats expected as it waits for it to process

aaelita

yep I have logs enabled

aaelita

gotcha, it seemed like it was taking longer but maybe this isn't abnormal behavior

Add a reply