# Web Component - Timeout **URL:** \ **Category:** Feedback\ **Created:** [October 19, 2017, 4:28pm UTC](https://community.thunkable.com/t/web-component-timeout/9295 "2017-10-19T16:28:34Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Nathaniel\_Hanks](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/nathaniel_hanks/32/2712_2.png) [@Nathaniel\_Hanks](https://community.thunkable.com/u/Nathaniel_Hanks)\ **Post date:** [October 19, 2017, 4:28pm UTC](https://community.thunkable.com/t/web-component-timeout/9295/1 "2017-10-19T16:28:34Z")
Being able to set a timeout on a web request is a standard setting and I am sure there is already a default time out value. A connection test is a great example of how setting a timeout could be useful, because it is simple request and should be quick in response. However, I found that the app would sit waiting for the response and you would already know that there is a connection issue. I suppose I could add a timer and create my own time out, but I feel a timeout value would be better. ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [November 8, 2024, 12:06pm UTC](https://community.thunkable.com/t/web-component-timeout/9295/2 "2024-11-08T12:06:07Z")