Skip to main content
Solved

Resource Exhausted Error in Query Metric Aggregates Request

  • May 3, 2023
  • 1 reply
  • 64 views

Forum|alt.badge.img+4

Hello Klaviyo Community,

I've been experiencing an issue with the Query Metric Aggregates Request (https://developers.klaviyo.com/en/reference/query_metric_aggregates) and receiving a "resource exhausted" error randomly. The problem is that this particular error is not listed among the Response Status Codes in Klaviyo's official documentation.

This issue has disrupted my processes, and I'm unable to figure out the root cause or possible solutions to resolve it. I kindly request assistance from the Klaviyo team or anyone familiar with this problem.

Any guidance or suggestions would be much appreciated. Please provide more information about the "resource exhausted" error and potential ways to mitigate it.

Thank you in advance for your help and support.
 

Best regards,

Sakthivel M

Best answer by Brian Turcotte

Hi @santiagosanti!

 

This error is similar to a 429 response in the sense that it’s telling you that there are too many calls being made to the endpoint at once. The difference is that it’s not caused by a rate limit policy, but rather system-level back-pressure.

 

Therefore, you will likely be able to account for this by including a Retry-After header. More information on that is included in our Developer Portal documentation here:

 

I hope this helps to clarify, and thanks for using the Community!

- Brian

View original
Did this topic or the replies in the thread help you find an answer to your question?

1 reply

Brian Turcotte
Forum|alt.badge.img+37

Hi @santiagosanti!

 

This error is similar to a 429 response in the sense that it’s telling you that there are too many calls being made to the endpoint at once. The difference is that it’s not caused by a rate limit policy, but rather system-level back-pressure.

 

Therefore, you will likely be able to account for this by including a Retry-After header. More information on that is included in our Developer Portal documentation here:

 

I hope this helps to clarify, and thanks for using the Community!

- Brian