The sequence is:
1/ It starts with the Loop branch but spend like 0 seconds and stops at the first node. That first node has no log of this “0s pseudo execution”
2/ It goes in the Done branch. Subflows work correctly there
3/ After Done branch, it goes to the Loop branch the correct number of times. Subflows work correctly there
4/ It end in the Done branch again. Subflows work correctly there
That is odd, It looks like the supabase node had an error though. You should be able to set the subworkflow to log under the workflows settings that will let us capture more attempts.
There is no log of the subworkflow where it lasts 0s, unless I make it crash at the beginning of it. I did went to the subworflow setting and saved “ON” everything possible.
Even if there was a bug or anything wierd inside that subworkflow, I don’t understand why it would go to the Done branch before going to the Loop branches
Actually the order is:
1/ Loop branch but without real execution of it
2/ Done branch
3/ Loop branch
4/ Done branch
5/ Loop branch
6/ Done branch
etc.
I have still not been able to reproduce this, In theory it should wait to loop back round unless we consider any failure a “done” option but I have tried with a few different error options with no luck as well.
Annoyingly as with any bug if it can’t be reproduced it makes it tricky to fix it, Does the same thing happen if you use a smaller workflow or less data maybe?
Import GetFeedback feedbacks from Campaign
