> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/integrations/relay-data-troubleshooting/requests.md).

# Requests

Review, filter, export, and troubleshoot integration relays in Settings → Integrations → Integration Requests.

Within your Anedot fundraising account, you can manage and review integration relay activity via **Settings → Integrations → Integration Requests**. This area allows you to:

* View and filter relay records
* Export data to CSV
* Troubleshoot failed relays

## Review Individual Relay Records

To inspect a specific relay:

1. Navigate to **Integration Requests**.
2. Click **View details** on the record you want to view *(or open the row timestamp)*.
3. A detailed view will open in a drawer on the right side of the screen, including status, request headers, request body, and response details.

## Filter Relay Records

Click **Filter** above the relay table. You can apply the following filters to help find specific relays:

* **Start/End Dates**
* **Relayed Entity Type**
* **Integration Service**
* **Integration ID**
* **Product Type**
* **Status**

## Export Relay Data

To download relay records:

* Click **Export all** in the upper-right corner of Integration Requests to generate a CSV file of relays.
* Click **Export failed** to download a CSV of failed records only.

## Troubleshoot Failed Relays

If an integration isn't working as expected, you can diagnose issues by reviewing failed relays:

### View Failed Records:

* From the **Integrations** directory: open **Integration Requests** in the sidebar *(or use Export failed on the Requests page)*.
* From **Integration Requests**:
  * Click **Export failed** *(upper right)* to download a CSV of failed records.
  * The export includes a **Response** column detailing the failure *(title, status, message, and status code)*.
  * For one or two failed relays, click **View details** and review the **Response body** for detailed error info.

### Understanding HTTP Status Codes:

* **200–299** = Success
* **400–599** = Failure *(e.g., **401 = Unauthorized**, often caused by incorrect login credentials)*

## Common Relay Failure Causes

**Single vs. All Pages** Make sure you’ve chosen whether the integration should apply to one specific page or **all pages**. Selecting all pages is recommended to future-proof your setup.

**Incorrect Login Credentials** Be sure to enter account name, username, and password correctly.

> *401 errors typically indicate authentication issues.*

**Unavailable Fields** Verify that the fields required for your integration are supported. Each integration has its own set of relayable fields—check documentation beforehand.

**Improper Template** By default, all available data is relayed. If using a custom template, ensure it’s configured correctly.

> *Leave the template field blank to send all data.*

**Expired or Missing SSL Certificate** SSL is required. Test your Webhook URL in a browser—if you see a security warning, your SSL may be expired or misconfigured.

**Endpoint Is Down** Check your Webhook endpoint:

* Load the URL in a browser (look for 404 or connection errors)
* Test the endpoint via [DNSChecker](https://dnschecker.org) for global availability

**Time Delays in Relays** Anedot relays are typically near real-time, but delays can occur during high server load. We use **exponential backoff retry logic** for failed relays—attempting multiple retries with increasing wait time.

## Resend Failed Relays

The **Push unsent** feature allows you to resend records that failed to relay while your integration was connected and active. It will not send data received before the integration connection date. Successful relays are not re-sent.

To manually re-push relays:

1. Go to **Settings → Integrations**
2. On the desired integration row, click **Push unsent**
3. Enter a **Start date** and **End date** *(up to 31 days apart; start cannot be more than 12 months ago)*
4. Confirm the relay scope *(Push failed only)* and click **Push unsent**

If successful, a new record will appear with a **Success** status. If issues persist, reach out to our [Support](https://www.anedot.com/getsupport) team for further assistance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.anedot.com/integrations/relay-data-troubleshooting/requests.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.