# Create row block not working well from yesterday

**URL:** https://community.thunkable.com/t/create-row-block-not-working-well-from-yesterday/887050
**Category:** Questions about Thunkable X
**Created:** [October 9, 2020, 1:40pm UTC](https://community.thunkable.com/t/create-row-block-not-working-well-from-yesterday/887050 "2020-10-09T13:40:30Z")
**Posts on this page:** 1
**Showing post:** 37

<div class="post-metadata">

### 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: [October 19, 2020, 10:06pm UTC](https://community.thunkable.com/t/create-row-block-not-working-well-from-yesterday/887050/37 "2020-10-19T22:06:30Z")

</div>

> [@Steven](#):
>
> Basically the simplest way to think about it is that if a block has a `then do` section, the block will begin to process whatever even it is for (create a row in this case) and will then continue on to the blocks beneath it while the code waits for a response on the initial function (again create row in this case), once that work is completed, the `do` section of the blocks will then run.

Awesome. Very clear! Thank you!

This repeat until method by @drted is then quite useful to halt the continuation of block evals: [Wrapping Asynchronous (then do) blocks into a Synchronous Function resolves unpredictable results](http://community.thunkable.com/t/wrapping-asynchronous-blocks-into-a-synchronous-function-for-the-win/910511).

I’ll have to go back to my project because it definitely wasn’t waiting and it definitely never displayed “B”. If I’m understanding you correctly, the expected behavior would be “A” then “C” immediately then “B” after two seconds. So I should be able to observe “C”…[two seconds]…“B”. What I’m seeing is just “C” (because “A” and “B” go by so quickly, I assume).

---

_[View the full topic](https://community.thunkable.com/t/create-row-block-not-working-well-from-yesterday/887050)._