# Asynchronous block functions **URL:** \ **Category:** Questions about Thunkable X\ **Created:** [May 28, 2021, 3:06pm UTC](https://community.thunkable.com/t/asynchronous-block-functions/1313620 "2021-05-28T15:06:42Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![drted](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/drted/32/92694_2.png) [@drted](https://community.thunkable.com/u/drted)\ **Post date:** [May 28, 2021, 8:33pm UTC](https://community.thunkable.com/t/asynchronous-block-functions/1313620/3 "2021-05-28T20:33:33Z")
Check out this technique > [@Wrapping Asynchronous (then do) blocks into a Synchronous Function resolves unpredictable results](https://community.thunkable.com/t/wrapping-asynchronous-then-do-blocks-into-a-synchronous-function-resolves-unpredictable-results/910511): > > Thunkable provides an extensive library of calls to external services including Google Docs and Web APIs. These external calls are, by necessity, asynchronous calls. That is, the request is sent to the external serivce, Thunkable block execution continues on it’s merry way, then the external service sends a reply. Thunkable wraps the external calls in in blocks with “Then Do” sections. This is a massive improvement over separate call and response block (MIT App Inventor), but it is not without … --- _[View the full topic](https://community.thunkable.com/t/asynchronous-block-functions/1313620)._