---
name: cloud-logs-agent-helm-retry-sending-data
title: Configure the number of retries sending data if an error occurs
description: When you deploy or upgrade the Logging agent, you can configure the `logs-values.yaml` file to set `retryLimit` and indicate whether the agent should retry sending the data to an IBM Cloud Logs instance.
last-updated: 2025-09-03
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/cloud-logs?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Configure the number of retries sending data if an error occurs
{: #agent-helm-retry-sending-data}

When you deploy or upgrade the Logging agent, you can configure the `logs-values.yaml` file to set `retryLimit` and indicate whether the agent should retry sending the data to an IBM Cloud Logs instance.
{: shortdesc}

After you modify the `logs-values.yaml`, you can [Upgrade the agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-agent-helm-update&format=markdown) or continue modifying the file before applying all the changes.

Valid values are:
- `false` to indicate that there is no limit for the number of retries that the scheduler can do. This is the default value.

    The entry in the `logs-values.yaml` file looks as follows:

    ```yaml
    retryLimit: false
    ```
    {: codeblock}

- An integer N value greater or equal to 1.

    The entry in the `logs-values.yaml` file looks as follows:

    ```yaml
    retryLimit: 8
    ```
    {: codeblock}

- *no_retries* to indicate that data is not sent to the destination if it failed the first time.

    The entry in the `logs-values.yaml` file looks as follows:

    ```yaml
    retryLimit: "no_retries"
    ```
    {: codeblock}

For more information, see the [Fluentbit documentation about retries](https://docs.fluentbit.io/manual/administration/scheduling-and-retries) to understand the implications of setting this value.

In some situations, this setting could lead to log data being discarded by the agent due to the inability to send.