run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-08-27 19:30:01 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

page separator not working on current llama parser version on python. #267

New Issue
Closed
opened 2026-02-16 00:17:19 -05:00 by yindo · 6 comments
yindo commented 2026-02-16 00:17:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @bilalayaz2 on GitHub (Sep 10, 2024).

Originally assigned to: @hexapode on GitHub.

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:

  • Python Library

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,
)

Originally created by @bilalayaz2 on GitHub (Sep 10, 2024). Originally assigned to: @hexapode on GitHub. _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: - Python Library **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, )
yindo added the bug label 2026-02-16 00:17:19 -05:00
yindo closed this issue 2026-02-16 00:17:19 -05:00
yindo commented 2026-02-16 00:17:19 -05:00
Author
Owner
Copy Link
Copy Source

@hexapode commented on GitHub (Sep 10, 2024):

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.

@hexapode commented on GitHub (Sep 10, 2024): 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.
yindo commented 2026-02-16 00:17:19 -05:00
Author
Owner
Copy Link
Copy Source

@bilalayaz2 commented on GitHub (Sep 10, 2024):

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.

@bilalayaz2 commented on GitHub (Sep 10, 2024): 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.
yindo commented 2026-02-16 00:17:19 -05:00
Author
Owner
Copy Link
Copy Source

@hexapode commented on GitHub (Sep 10, 2024):

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

@hexapode commented on GitHub (Sep 10, 2024): 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
yindo commented 2026-02-16 00:17:19 -05:00
Author
Owner
Copy Link
Copy Source

@hexapode commented on GitHub (Sep 10, 2024):

What version of the python package are you using we are currently at 0.5.5 on python

@hexapode commented on GitHub (Sep 10, 2024): What version of the python package are you using we are currently at 0.5.5 on python
yindo commented 2026-02-16 00:17:20 -05:00
Author
Owner
Copy Link
Copy Source

@bilalayaz2 commented on GitHub (Sep 11, 2024):

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.

@bilalayaz2 commented on GitHub (Sep 11, 2024): 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.
yindo commented 2026-02-16 00:17:20 -05:00
Author
Owner
Copy Link
Copy Source

@DarkShark-RAz commented on GitHub (Dec 7, 2024):

I have similar problem with llama parse and I am using 3.11.9 python with latest llama-parse.

@DarkShark-RAz commented on GitHub (Dec 7, 2024): I have similar problem with llama parse and I am using 3.11.9 python with latest llama-parse.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#267
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?