# "Looping" a loop **URL:** \ **Category:** Questions about Thunkable X\ **Tags:** beginner\ **Created:** [June 11, 2021, 5:55pm UTC](https://community.thunkable.com/t/looping-a-loop/1339687 "2021-06-11T17:55:10Z")\ **Posts on this page:** 1\ **Showing post:** 6
**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 11, 2021, 7:57pm UTC](https://community.thunkable.com/t/looping-a-loop/1339687/6 "2021-06-11T19:57:08Z")
Nested loops can work in Thunkable but there are quite a few components that take too long to complete their code and don’t work inside of loops. You’re using a _stored_ variable which is a slower method of storing/retrieving data in Thunkable. I wonder what happens if you use an _app_ variable? It’s very possible that you’re going to need to add some `Wait` blocks (possibly just wait 0 seconds) within the loop block(s) to slow things down. Some very relevant info: > [@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/looping-a-loop/1339687)._