---
title: "Retry on RESOURCE_EXHAUSTED failure | Grafana Cloud documentation"
description: "Cloud Traces returns RetryInfo to correctly indicate retryable errors. RESOURCE_EXHAUSTED is a retryable error. The collector will keep data and attempt to send data again after an interval returned by the server."
---

# Retry on `RESOURCE_EXHAUSTED` failure

Grafana Cloud Traces returns `RetryInfo` to correctly indicate retryable errors. This change aligns with the OpenTelemetry specification. As per the [OTel specification](https://opentelemetry.io/docs/specs/otlp/#failures), “Retryable errors indicate that telemetry data processing failed, and the client SHOULD record the error and may retry exporting the same data. For example, this can happen when the server is temporarily unable to process the data.” If an error is retryable, the collector keeps the data and attempts to send again after the interval returned by the server.

## Impact

If configured to retry, OTel Collector and Grafana Alloy telemetry collectors correctly retry for retryable errors. Incorrectly configured collectors might hold too much data in memory and run out of memory and crash. The amount of data a collector holds in memory to retry can be controlled using `sending_queue` and `retry_on_failure` configuration options.

For Grafana Alloy, refer to [`sending_queue`](/docs/alloy/latest/reference/components/otelcol.exporter.otlp/#sending_queue-block) and [`retry_on_failure`](/docs/alloy/latest/reference/components/otelcol.exporter.otlp/#retry_on_failure-block) in Grafana Alloy.

For OpenTelemetry Collector, refer to `sending_queue` and `retry_on_failure` in the [Configuration section of the README](https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/exporterhelper/README.md?rgh-link-date=2024-05-24T13%3A10%3A40Z#configuration).