ERROR_DURING_PROCESSING: An unknown error occurred during processing. #396

Closed
opened 2026-02-16 00:17:43 -05:00 by yindo · 1 comment
Owner

Originally created by @JohanBekker on GitHub (Jan 2, 2025).

Describe the bug
Using the LlamaParse API, more often than not, the document processing call returns an error after 1800 seconds. This happens for both small documents (like 5 pages), and for documents of 50+ pages. Uploading the same document through the frontend UI did seem to work, but that might have been chance.

I found a similar ticket marked as closed, but as of now this issue is not resolved and it is blocking us from releasing a new functionality to production. We do have a retrying mechanism but this is not the solution to the problem. We expect documents to be processed in a reasonable timespan (couple minutes), and not have it fail after 30 minutes and retried until it finally works after a couple of tries.

Job ID
It is not a singular event.

Client:
Please remove untested options:

  • API
  • Frontend (cloud.llamaindex.ai)

Additional context

{
          "language": Language.ENGLISH.value,
          "parsing_instruction": "",
          "invalidate_cache": False,
          "skip_diagonal_text": False,
          "do_not_cache": False,
          "fast_mode": False,
          "premium_mode": False,
          "continuous_mode": False,
          "do_not_unroll_columns": False,
          "gpt4o_mode": False,
          "gpt4o_api_key": None,
          "vendor_multimodal_api_key": None,
          "use_vendor_multimodal_model": False,
          "vendor_multimodal_model_name": None,
          "take_screenshot": True,
          "disable_ocr": False,
          "is_formatting_instruction": False,
          "annotate_links": False,
}
Originally created by @JohanBekker on GitHub (Jan 2, 2025). **Describe the bug** Using the LlamaParse API, more often than not, the document processing call returns an error after 1800 seconds. This happens for both small documents (like 5 pages), and for documents of 50+ pages. Uploading the same document through the frontend UI did seem to work, but that might have been chance. I found a similar ticket marked as closed, but as of now this issue is not resolved and it is blocking us from releasing a new functionality to production. We do have a retrying mechanism but this is not the solution to the problem. We expect documents to be processed in a reasonable timespan (couple minutes), and not have it fail after 30 minutes and retried until it finally works after a couple of tries. **Job ID** It is not a singular event. **Client:** Please remove untested options: - API - Frontend (cloud.llamaindex.ai) **Additional context** ``` { "language": Language.ENGLISH.value, "parsing_instruction": "", "invalidate_cache": False, "skip_diagonal_text": False, "do_not_cache": False, "fast_mode": False, "premium_mode": False, "continuous_mode": False, "do_not_unroll_columns": False, "gpt4o_mode": False, "gpt4o_api_key": None, "vendor_multimodal_api_key": None, "use_vendor_multimodal_model": False, "vendor_multimodal_model_name": None, "take_screenshot": True, "disable_ocr": False, "is_formatting_instruction": False, "annotate_links": False, } ```
yindo added the bug label 2026-02-16 00:17:43 -05:00
yindo closed this issue 2026-02-16 00:17:43 -05:00
Author
Owner

@JohanBekker commented on GitHub (Feb 11, 2025):

Haven't seen this problem in a while so I assume it is fixed. Thanks though for the communication.

@JohanBekker commented on GitHub (Feb 11, 2025): Haven't seen this problem in a while so I assume it is fixed. Thanks though for the communication.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#396