Automation switches from "failed" to "in progress" and gets stuck there

An automation in Tape initially shows as ā€œFailedā€ in the run log. When expanded, the status switches to ā€œIn Progressā€ but never completes, even though all steps execute successfully. The automation in this example only collects related fields and performs no other actions. This behavior is only observed in one specific Tape instance and could not be reproduced in others.

Steps to Reproduce:

  1. Run an automation that collects related fields.
  2. Observe the run log showing ā€œFailed.ā€
  3. Expand the log entryā€”status changes to ā€œIn Progress.ā€
  4. Despite all steps completing, the automation never finishes.

Expected Behavior:
The automation should complete and show a ā€œSuccessā€ status.

Actual Behavior:
The automation remains stuck in ā€œIn Progressā€ indefinitely.

Before Expansion

After Expansion

Edit:
After further investigation, it only happens after at least two related Records are collected.
Unfortunately it happens only with collection some specific Apps, but I couldnā€™t find any similarities between those App records to identify a pattern.

1 Like

Hi @Eric_Scherlich,

thank you very much for the report and the detailed preparation of how we can create the behavior.

We will analyze the issue in detail and will provide a fix for it. I think with the great analysis from your side we will quickly come to a solution.

Thanks again and best regards
Leo

Iā€™ve just had the same issue

image

I got a webhook failed notification but the flow still show in progress with no failed log.

this happens consistently with this specific flow:

The issue was found.

Do you happen to try to collect from 2 (or more Apps) where one was created by copying the other?
If thats the case look at the singular name of the entries, if they both have the same name then thats the cause of the bug.

1 Like

If I understand you correctly then no, I donā€™t do that.
Iā€™m just collecting a webhook payload > searching an app for a marching record and creating/updating a record depending on if the record was found or not.

Itā€™s definitely something to do with the search though

When that is deactivated everything works. As soon as itā€™s on, everything just fails and then pauses on ā€˜In progressā€™

Itā€™s only that one specific app it fails on. Iā€™ve tried seaching other fields within that app and each one fails. Iā€™ve tried searching other apps and everything works as expected.

@Leo - Do you want me to open another thread for this seeing as this one is marked as ā€˜Doneā€™ or keep it here?

1 Like

Hi @martin_e,

thanks for the report! We can leave it here. Weā€™ll take another look at your problem in detail and fix it! We will get back to you with an update.

Best
Leo

1 Like