What is the difference between disabled and enabled of "Wait for execution to complete?"?

[leinharte]

Hi, everyone.

My work has these 3 steps:
< 1step >
To register transactions to the transaction table.

< 2step: rowTotal >
To sum the transaction amount with each account by running the process of Call a webhook.

< 3step: subTotal >
To sum the rowTotal of the first step of the bot to the subTotal by running the process of Call a webhook.

※ The transaction table is as follows.

※ The report table is as follows.

※ I have 5 bots. And this is the result of running each bot.

no	the name of each bot	the process of each bot	Wait for execution to complete?	report table after running each bot
1	rowTotal	- rowTotal	n/a
2	subTotal	- subTotal	n/a
3	rowTotal_subTotal	- rowTotal - subTotal	n/a
4	rowTotal_triggerSubTotal_disabled	- rowTotal - triggerSubTotal	disabled
5	rowTotal_triggerSubTotal_enabled	- rowTotal - triggerSubTotal	enabled

[Question] 

Like the result, there is no difference between no.4(disabled) and no.5(enabled).

BTW, what I expect from disabled is this:

What is the difference between disabled and enabled of "Wait for execution to complete?"?

Thank you.

[Marc_Dillon]

That option is typically helpful for large-scale API operations involving a lot of records that could take a lot of time, but you don't want the app user to have to wait for them to complete for their sync to finish. Sometimes the user needs the updated data before they can do something else, and sometimes they do not, switch the option appropriately.

[leinharte]

@Marc_Dillon  Thanks for your comment.

I believe my understanding of that option is the same as yours. To verify my understanding, I had created a sample app and checked it. That is, summing the values ​​of the transaction table into the report table (hereinafter referred to as "rowTotal") and adding up the aggregated values ​​again within the report table (hereinafter referred to as "subTotal"). I had tried this(rowTotal and triggering subTotal) for each option, but contrary to my expectations, the results for each option were the same.

Is there something I'm missing?

Thanks.

[Marc_Dillon]

I think I see what you're getting at with your tests. The final process requires having the data produced by the earlier processes, right? They are all failing to produce the final subtotal, correct?

I think I'd have to see further details of the bots in order to make a guess as to what is happening.

[leinharte]

Yes, that's what I am trying to do.

I have no idea how to share the test app with you. I'd explain the test app here.

tables

action

Bots
bot1: subTotal

subTotal step

bot2: rowTotal_triggerSubTotal_disabled

rowTotal step

triggerSubTotal step

options

bot3: rowTotal_triggerSubTotal_enabled
bot3 is same with bot2 except this option:

=> The bot2 and the bot3 have a same result like this.
before running bot:

after running bot:

Thanks.

[leinharte]

I got to know how to share an app. This is my test app.

test