# Last item displayed first when Cloning **URL:** \ **Category:** Questions about Thunkable X\ **Created:** [June 8, 2021, 6:27am UTC](https://community.thunkable.com/t/last-item-displayed-first-when-cloning/1332081 "2021-06-08T06:27:37Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\ **Post date:** [June 9, 2021, 3:42am UTC](https://community.thunkable.com/t/last-item-displayed-first-when-cloning/1332081/7 "2021-06-09T03:42:21Z")
Me neither! I just know that cloning or creating a block within a loop requires some delay. Otherwise, the component creation happens too quickly. And even though it’s a wait 0 seconds block, it still causes a delay because the screen has to refresh each time (so I’ve been told). If you want to learn more, see this: > [@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/last-item-displayed-first-when-cloning/1332081)._