Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Printing Large Amounts of Data Fails #560

Closed
stdavis opened this issue Aug 28, 2023 · 2 comments
Closed

Printing Large Amounts of Data Fails #560

stdavis opened this issue Aug 28, 2023 · 2 comments
Assignees
Labels
Milestone

Comments

@stdavis
Copy link
Member

stdavis commented Aug 28, 2023

Image

Load some of these layers into a AGOL web map and see if it has the same issues.

Perhaps we can add a feature result limit.

@stdavis stdavis added the bug label Aug 31, 2023
@stdavis stdavis added this to the v2 milestone Sep 28, 2023
@stdavis stdavis self-assigned this Jan 9, 2024
stdavis added a commit that referenced this issue Jan 9, 2024
@stdavis stdavis assigned nathankota and unassigned stdavis Jan 12, 2024
@nathankota
Copy link

Attempted to mimick the query in the initial issue comment relatively closely. The map view worked, but the layout view set to pdf output format and the other default settings failed multiple times.

Image

@nathankota nathankota assigned stdavis and unassigned nathankota Jan 18, 2024
@stdavis
Copy link
Member Author

stdavis commented Feb 1, 2024

I'm not sure that there is a lot that we can do here. I believe that this is a mix of the print proxy request to the AGOL print service timing out and the browser request to print proxy (via the print widget) timing out. I tried increasing the browser request timeout using esri.config.request.timeout but that didn't seem to have any effect on the request coming from the print widget.

I did fix a few bugs in print proxy that should help with layout templates. I also bumped the node version so maybe that will help with performance? Although, it's not print proxy itself that's timing out.

I think that in the end, folks are just not going to be successful printing 10's of 1000's of features. I'm not sure how valid that use case is anyway.

@stdavis stdavis closed this as completed Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

2 participants