---
title: UDS Intermittent Timeout Failure
description: Issue Description The provider is invoking our UDS (Universal Data Sync) flow; however, the requests are failing intermittently due to a timeout. This occurs when the provider does not send a response within the configured action timeout duration. ...
url: "https://supportb.kinsta.cloud/docs/uds-intermittent-timeout-failure/"
updated: "2026-02-17"
category: "Apps: Lead Capture"
---

# UDS Intermittent Timeout Failure

## Issue Description

The provider is invoking our UDS (Universal Data Sync) flow; however, the requests are failing intermittently due to a timeout.

This occurs when the provider does not send a response within the configured action timeout duration.

## Root Cause

The **Action Timeout** defines the maximum duration within which the provider must respond to the UDS request.

- UDS is configured to retry the request **3 times** if no response is received.
- If the provider fails to respond within the configured timeout during all three attempts, the request ultimately fails.
- For example, if the logs show a timeout at **31 seconds**, this indicates:
  - The action timeout was set to **10 seconds**
  - UDS retried **3 times**
  - Total elapsed time ≈ 30 seconds (plus processing overhead)

## Resolution Steps

To increase the timeout limit:

1. Open the **UDS Flow**
2. Click on **Edit**
3. Navigate to **Advanced Options**
4. Increase the **Action Timeout** limit
5. Save and publish the changes

   ![](https://desk.zoho.in/galleryDocuments/edbsn3cbd7f5622379bbefd376eab95a89293f4cd610792b51a06dd6a9f073e87a396296ab2bb769bdc69665022ed604fb3f48513ded0b90bfff74dee5f3015111b86)

## Important Notes

- The Action Timeout should be configured based on the provider’s average response time.
- If the provider consistently takes longer to respond, they should optimize their response time.
- Increasing the timeout temporarily can help mitigate intermittent failures, but the long-term fix should ensure the provider responds within the configured limit.