# Ensuring Reliable Data Transfers: Retry Configuration

### Introduction

In data workflows, failures can occur due to network interruptions, server downtimes, or credential mismatches. To address such failures, a retry mechanism is essential—if something fails, the system must automatically retry to ensure successful data delivery.

### Configuring Retry Parameters

**Step 1:** In the navigation panel, click **Pipeline**.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FPu4FvNszzeYBl3z2xz5Z%2Fimage.png?alt=media&#x26;token=9cca5450-ad02-42c1-bae1-5ea2057dc4e7" alt=""><figcaption></figcaption></figure>

**Step 2:** A list of pipelines appears. Click the pipeline you wish to open.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FYQMTGBQsuoDF3BWRdE7Y%2Fimage.png?alt=media&#x26;token=5b707974-59fc-4b56-9940-babb565c403e" alt=""><figcaption></figcaption></figure>

**Step 3:** Click **Destinations**.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FU2WAg579lQa9AWJnQGdF%2Fimage.png?alt=media&#x26;token=77378bdb-3a99-4be3-bcc9-30cd9fa1f22f" alt=""><figcaption></figcaption></figure>

**Step 4:** under the **Type** column, you can see different types of databases. These indicate the data storage systems where data from the server will be pushed to the destination.

If one of the destinations fails, for example, while transferring data to two destinations, the system will automatically retry the operation for the failed destination until the transfer is successful.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FFs0jwsCTRm3tgPcmDTtJ%2Fimage.png?alt=media&#x26;token=03cfaf7e-afc7-4c4c-90c9-41c458efe945" alt=""><figcaption></figcaption></figure>

**Step 5:** Click the **Settings** button to configure the retry mechanism for destinations.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FnQNw5sTrIxvSJOMyvCbL%2Fimage.png?alt=media&#x26;token=29b5dc9d-7f93-4d78-9c47-9e226e09f521" alt=""><figcaption></figcaption></figure>

**Step 6:** Click **Retry Configuration** to access the retry settings.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FtNWBPtrRI4t2vZzJhP3A%2Fimage.png?alt=media&#x26;token=25c04084-a17a-4e37-a01f-a95807293484" alt=""><figcaption></figcaption></figure>

**Step 7:** Click the **Edit** button to modify the retry parameters.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2Fnl2IiFpQRIFAPAc6ccQR%2Fimage.png?alt=media&#x26;token=4487fcad-cb84-4d43-90ca-e8f50e7cf5ff" alt=""><figcaption></figcaption></figure>

**Step 8:** Check the **Enable** checkbox.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FKK1iMn0JdcwMQ8ugVhC5%2Fimage.png?alt=media&#x26;token=6d119093-b027-4a78-b9e5-51177022e974" alt=""><figcaption></figcaption></figure>

**Step 9:** Under **Retry After**, you will see a dropdown with options such as **Seconds**, **Minutes**, and **Hours**. You can enter a number in the **Retry After** field to specify the retry interval. Then, choose whether you want the system to retry after a specific number of seconds, minutes, or hours.

For example, if you enter 2 in the **Retry After** field and select **Hours**, the system will retry the operation every 2 hours until it succeeds.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FpjJfWkwvxpGhr8ezsH0B%2Fretry%20num%202.png?alt=media&#x26;token=c96ba5a6-0f2d-4dfa-ab74-2aaaf28c998c" alt=""><figcaption></figcaption></figure>

**Step 10:** Under **Maximum Attempts**, you can specify the maximum number of retry attempts. The system will retry the operation until the specified number of attempts is reached, after which it will stop retrying, even if the operation has not succeeded.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FnLLqlLaPbJiP7XEj8gau%2Fretry%20one.png?alt=media&#x26;token=e62d9dc8-3990-4710-ab9b-c6ce1930c203" alt=""><figcaption></figcaption></figure>

**Step 11:** Click the **Save** button to save your retry configuration settings.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FsvkrlP5GB8mIZLYOFUoj%2Fretry%20save.png?alt=media&#x26;token=95f8889d-65ec-48a8-9538-80a4f0b95c47" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ingestlabs.com/media-data-platform/pipelines/ensuring-reliable-data-transfers-retry-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
