You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: we're aware of some missing content in the output and layout issues on tables. Please refrain from opening new issues on this topic unless if you think it's different from what has already been reported.
Describe the bug
Llama parse current version's page separator parameter is not functional while accessing through the api.
Could you share a job_id with us where you envcounter the issue, we were not able to reproduce when using the api? You can found them in the history tab of cloud.llamaindex.ai/parse for past jobs.
I just tried it again for you to give you a job_id but the history tab did not update so i currently have no job_id at hand.
And the same code works in llama-parse==0.4.9 on python.
We just update the history tab if you log now, it should allow you to see:
Job id
What went wrong during the parsing (page by page granularity)
The output
I'm facing this issue on llama-parser 0.5.5 and tried on both python 3.12.0 and 3.12.6
Job-id = 26064475-e158-4eb1-8ade-49ed0dc25528
The result in job details on the history tab does contain the page separator but the response from the api thats saved as markdown does not have this page separator, but when I use llama-parse 0.4.9, page separator is present in the file saved.
Note: we're aware of some missing content in the output and layout issues on tables. Please refrain from opening new issues on this topic unless if you think it's different from what has already been reported.
Describe the bug
Llama parse current version's page separator parameter is not functional while accessing through the api.
Client:
Please remove untested options:
Options
parser = LlamaParse(
api_key=self.api_key,
parsing_instruction=self.pi,
language="en",
page_separator="|======================|",
result_type=self.result_type,
do_not_cache=True,
invalidate_cache=True,
)
The text was updated successfully, but these errors were encountered: