- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
10-10-2018 02:57 PM
10-12-2018 08:36 AM
That limit is there to protect ourselves from hanging connections. In our opinion, 5 seconds is plenty of time for the UDH to make a request out to an endpoint, but more importantly for that endpoint to accept the request and respond.
To me, this is more of an issue with the endpoint. Either it's down, or it's not processing the incoming requests fast enough that it is lagging. May I ask what endpoint is being used?
10-25-2018 09:27 PM
This endpoint is used to receive updates from the AudienceStream profile, we get a snapshot of the user profile at the end of the session, so, sometimes the amount of transactions that we get are very high, so wanted to see if there is a way to enable retries or increase the timeout.
10-26-2018 10:39 PM
Unforunately not. I'd suggesting submitting this idea at https://community.tealiumiq.com/t5/Product-Ideas/idb-p/product-ideas so it can be reviewed.
10-29-2018 02:13 AM
@yehohanan What is the current logic for triggering the webhook? Is it simply every visitor at the end of every visit? Would it make sense in your case to only send the webhook if at least one of the data variables you are sending has changed in the current visit?
Copyright All Rights Reserved © 2008-2023