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

Cannot access enterprise account #558

New Issue
Open
opened 2026-02-16 00:18:15 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 00:18:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @alexandermorganDM on GitHub (Oct 15, 2025).

Describe the bug
When I sign in to LlamaCloud and then try to change my organization to my company's main account, I get this error:
"Unknown Error
Minified React error #321; visit https://react.dev/errors/321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings."

I'm not sure if it's related but yesterday when I was uploading files I was also no longer able to poll the list of current jobs with the /jobs endpoint that was previously accessible via the client.pipelines.list_pipeline_jobs() function. It started returning a 404.

Files
N/A

Job ID
N/A

Client:
Please remove untested options:

  • Python Library
  • API
  • Frontend (cloud.llamaindex.ai)
  • Typescript Library
  • Notebook

Additional context
Having the frontend down and also some api calls no longer working, I'm unable to manage my company's LlamaCloud indexes. This is a major blocker for us.

Image
Originally created by @alexandermorganDM on GitHub (Oct 15, 2025). **Describe the bug** When I sign in to LlamaCloud and then try to change my organization to my company's main account, I get this error: "Unknown Error Minified React error #321; visit https://react.dev/errors/321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings." I'm not sure if it's related but yesterday when I was uploading files I was also no longer able to poll the list of current jobs with the /jobs endpoint that was previously accessible via the client.pipelines.list_pipeline_jobs() function. It started returning a 404. **Files** N/A **Job ID** N/A **Client:** Please remove untested options: - Python Library - API - Frontend (cloud.llamaindex.ai) - Typescript Library - Notebook **Additional context** Having the frontend down and also some api calls no longer working, I'm unable to manage my company's LlamaCloud indexes. This is a major blocker for us. <img width="623" height="501" alt="Image" src="https://github.com/user-attachments/assets/cca409a8-9ad3-4ac0-be93-0a22064762bb" />
yindo added the bug label 2026-02-16 00:18:15 -05:00
yindo commented 2026-02-16 00:18:15 -05:00
Author
Owner
Copy Link
Copy Source

@alexandermorganDM commented on GitHub (Oct 15, 2025):

Similar to this closed issue.

@alexandermorganDM commented on GitHub (Oct 15, 2025): Similar to this [closed issue](https://github.com/run-llama/llama_cloud_services/issues/659).
yindo commented 2026-02-16 00:18:15 -05:00
Author
Owner
Copy Link
Copy Source

@alexandermorganDM commented on GitHub (Oct 15, 2025):

Connecting programmatically, I see that our project has been disabled without warning or explanation. Can we have an update on this issue?

@alexandermorganDM commented on GitHub (Oct 15, 2025): Connecting programmatically, I see that our project has been disabled without warning or explanation. Can we have an update on this issue?
yindo commented 2026-02-16 00:18:15 -05:00
Author
Owner
Copy Link
Copy Source

@MartijnLeplae commented on GitHub (Oct 28, 2025):

Have you heard any updates from the LlamaCloud team? I would at least expect better support for Enterprise customers.

For good measure, are you sure you have correct access rights, selected the right region etc?

@MartijnLeplae commented on GitHub (Oct 28, 2025): Have you heard any updates from the LlamaCloud team? I would at least expect better support for Enterprise customers. For good measure, are you sure you have correct access rights, selected the right region etc?
yindo commented 2026-02-16 00:18:15 -05:00
Author
Owner
Copy Link
Copy Source

@alexandermorganDM commented on GitHub (Oct 28, 2025):

Yes, our issue was that we exceeded the allowable number of documents but kept requesting to submit more because it was an automated process. The LC team reinstated access to our account quickly although I'm still not sure of a permanent solution to the root problem. I also wouldn't be able to tell if the actual bug of freezing an account without explanation is fixed, so this is out of my hands at this point.

@alexandermorganDM commented on GitHub (Oct 28, 2025): Yes, our issue was that we exceeded the allowable number of documents but kept requesting to submit more because it was an automated process. The LC team reinstated access to our account quickly although I'm still not sure of a permanent solution to the root problem. I also wouldn't be able to tell if the actual bug of freezing an account without explanation is fixed, so this is out of my hands at this point.
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#558
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?