Relay records can be viewed within Settings>Integrations>Requests tab of the fundraising account. Within the Requests tab, you may review and filter relay records, export data into CSV, and troubleshoot failed relays.
Review Individual Relays
To review an individual relay record, click on the associated record's Timestamp. The relay record details will open in a drawer on the right side of the page.
Filter Relay Records
The following Filters can be applied to sort through relays:
Start/End Dates
Relayed Entity Type
Integration Service
Integration ID
Product Type
Status
Download Data in CSV Format
Export your relayed data into a CSV file by clicking the Export All button in the upper right corner of the page.
Troubleshoot Failed Relays
We provide a relay export for our submission integrations that can help you troubleshoot why your integration is not working.
To access the failed relay records for your integrations, hover over Actions and select Show Requests if you are accessing from the Directory tab. If accessing from the Requests tab, follow the next step below.
If you have multiple failed relays, click on the Export Failed button in the upper right corner of the Requests tab to download a CSV report. The report will include a Response column outlining the cause of the failed relay through the title, status, message, and status code.
If you only have one or two failed relay records, click on the Timestamp associated with each record to review the Response Body for error details.
You may use the "HTTP response status codes" documentation to identify why your data did not pass through properly. 200-299 responses reflect that data was passed successfully. 400-599 responses will reflect data that was not passed properly and why. For example, 401 may reflect that you have incorrect login information for your integration.
Continue to the steps below to learn about each potential cause for failure.
Single vs. All Pages
As you're setting up your integration, be sure to select if you want to pass through data from a specific page or for all pages. If you have one page to start but may create more later, we recommend selecting all pages. When all pages have been selected, any new pages will be included for future data relays.
Incorrect Login Credentials
Some integrations require you to type in an Account Name, User Name, and/or password to connect to that integration. You must type this information correctly, or the other app will not accept our data.
If an integration has incorrect login credentials, that will likely show up on a Failed Relays Report as a 401 error.
Field Unavailable
Each integration will have different fields available. This is dependent on what fields the platform has available. Before setting up a connection, please review the Data Relays noted for each integration to verify that the data you need can be passed successfully.
Improper Template
By default, our integration templates pass all available data. However, you have the option to limit the data that is passed by applying a custom template.
If you would like all available data to be passed, we recommend leaving the Template field blank.
Expired SSL
Your integration may be failing due to a lack of SSL on your endpoint or due to an expired certificate. Anedot requires SSL for security reasons as we relay Personally Identifiable Information (PII).
To check if you have an expired SSL, load the Webhook URL into your browser to confirm a security notice is received.
Endpoint Down
If the endpoint you are connected to is down, this will cause relays to fail. If this occurs, recommend reviewing the following:
Attempt to load the Webhook URL into your internet browser. If it has a "not found" error, then that endpoint is down.
Check your URL at https://dnschecker.org/. If your endpoint is down, you will see it as "Not Resolved" on the world map.
Time Delays in Relays
When an attempt to relay a webhook or integration fails, we continue to attempt to retry this integration and track when specific donations are not sent. Our relays begin with an exponential backoff where we retry the relay with less frequency as more failures occur.
Generally, data should be relayed from Anedot to your app in near real-time. There can be circumstances though where this is delayed due to high server load. If so, don't panic! If you are ever in doubt, you can check the Failed Relays Report to confirm if a relay failed.
Resending Relays
If a relay has failed, you may attempt to re-push the relay(s) that did not pass successfully. To do so, follow the steps below:
Access the Settings>Integrations>Directory tab.
Hover over the integration.
Click Actions>Push Unsent.
Next, enter a date range and choose to send only failed relays.
If the relay has been passed successfully, a new Success record will be available. If the relays continue to fail, you may contact our Support team for further assistance.