[DONE] Loop gets overtaken by other loop in logs

šŸ”§ Bugs & Issues
,
1

Iā€™ve been trying for 4 hours to create a simple loop over an array. But the automation isnā€™t behaving as expected; it iterates through the loop faster than a loop needs to complete. How can I solve this simple problem in Tape?

I have an array with three IDs [3665, 6989, 8304]. Now I want to check each of these IDs for existence. If an ID doesnā€™t exist, I will create a corresponding entry.

The problem is that the actions in the loop arenā€™t starting one after another. It almost seems like all three loops start at the same time and mess everything up.

Here is a simple example that already fails.

image
image1920Ɨ2169 232 KB

I would really appreciate it if someone could help me please. :pray: :exploding_head:

2

I think I covered a way around this on the latest Tape Webinar. See here (hopefully it can help)

2 Likes
3

I totally get your frustration. Iā€™ve run into similar situations.

We have a few scenarios where weā€™re hitting race conditions. We need to be sure about two things:

  1. Does a block wait for the previous one to finish?
  2. Are loops running sequentially?
  3. Is a fields value written within an automation block already there, when I read it in a following block again (e.g. as a condition)?

If the answer is ā€˜yesā€™ to them, then something is wrong. Enforcing these would definitely help us avoid these issues.

1 Like
4

What about a wait-for-completion option in the loop function?

image
image1080Ɨ632 57.2 KB

I think that would help some users from the no-code communityā€¦

3 Likes
5

Hi @Roman,

Many thanks for the report, we really appreciate you taking the time to describe the issue so clearly.

We are currently looking into this in more detail to understand what the best solution for your case is. Weā€™ll get back to you soon with feedback and ideally also a fix for the problem.

Thanks again for reporting this and helping us improve Tape :100:

Best regards and have a great weekend,
Leo

6

Hi @Roman,

thanks for the detailed report and your patience. :100:

We were able to reproduce your scenario, and discovered a display bug that would sometimes mess up the order of executed actions inside the workflow logs when actions quickly follow each other.

This seems to be exactly the scenario that led to the confusion. Luckily, we were able to resolve this now, and the update is live. :train2: Newly created and also past workflow runs should now display the action logs in proper order, without any ā€œovertakingā€ going on. In our scenario this is working as expected now, would be great if youā€™d confirm on your end.

This screenshot also demonstrates a simplified scenario with logs (now correct):

Screenshot 2026-03-18 at 17.16.36
Screenshot 2026-03-18 at 17.16.362564Ɨ1938 484 KB

ā€¦ Which brings us to the next issue raised here (also by @dirk_s): Loops in Tape are indeed fully sequential. As long as users do not leverage custom code to explicitly work around that behavior (also worth noting that the video @Luis regarding await is a great watch for advanced users), all actions will execute consecutively after each other. :hourglass_flowing_sand:

:bulb: Important caveat: Your screenshot shows a ā€œTrigger automationā€ action. Note that your run cannot and will not wait for the triggered execution to run; it will basically trigger the run using fire and forget. Once that other run is triggered, it will run in parallel (of course respecting your organization capacity).

Hopefully this can clarify things a bit, and will help finalizing your use case. If you still run into issues, be sure to share them here in the thread so the Tape community is fully enabled to help :eyes: :blue_heart:

Cheers & happy Wednesday
Tape dev team

1 Like