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:
Run an automation that collects related fields.
Observe the run log showing āFailed.ā
Expand the log entryāstatus changes to āIn Progress.ā
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.
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.
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.
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.
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?