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:
Open the UDS Flow
Click on Edit
Navigate to Advanced Options
Increase the Action Timeout limit
Save and publish the changes
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.
Related Articles
Data fetch issue | Activity based reports
Issue reported: The "Activities by User (Historical)" report does not fetch the complete data of all the activities selected using the "Activity Type(s)" dropdown. Solution/ Findings: This is the default behaviour of the system wherein: 1. If there ...Automation Cards Failure email alerts
The Automation Failure notification will trigger only those who created the automation and who modified the automation. Please note all the users who modified the automation will get the automation failure notification (e.g.: if user-a modified the ...How to find correct mapping key in UDS?
The leads are not being properly utilized, created or some error in UDS logs in the system due to incorrect field mapping configured in the UDS. To resolve this, we recommend updating the mapping by using the correct field structure as identified ...How to use Mavis data in SIERA report
First, check if the same is enabled or not. If not needs to be enabled from backend(Advait). You need to navigate to Mavis Table>Reports>Select the Columns you wish to sync to SIERA and save it. It takes few minutes based on data stored to sync the ...Deletion of Leads in Sandbox Account after Sync
Query: The client is questioning the reason behind the deletion of all leads in the sandbox account after performing a sync. Reason: During the sync process, all configurations from the production account are copied to the sandbox account, depending ...