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

Error: grpc: received message larger than max... #43

Closed
1 of 4 tasks
issacg opened this issue May 16, 2019 · 2 comments
Closed
1 of 4 tasks

Error: grpc: received message larger than max... #43

issacg opened this issue May 16, 2019 · 2 comments
Labels
bug ⚠️ Something isn't working in the library

Comments

@issacg
Copy link

issacg commented May 16, 2019

I'm submitting a ...

  • bug report
  • feature request
  • question about the decisions made in the repository
  • question about how to use this project

Summary

I've run into scenarios when running a query returns the following error "Error: Received message larger than max (9154892 vs. 4194304)"

Other information

t CustomerService. (C:\prj\node_modules\google-ads-api\build\services\service.js:205:23)
at Generator.throw ()
at rejected (C:\prj\node_modules\google-ads-api\build\services\service.js:5:65)

@kritzware kritzware added the bug ⚠️ Something isn't working in the library label May 16, 2019
@kritzware
Copy link
Contributor

Hi @issacg, unfortunately I'm not sure there is much we can do about this issue. I believe this comes from the grpc-node library that we're using internally.

Which queries does this happen for? Is there any way you can limit the results you're retrieving, using the limit constraint?

@avermeil
Copy link
Member

Fixed in 2.1.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug ⚠️ Something isn't working in the library
Projects
None yet
Development

No branches or pull requests

3 participants