Delete Files/Folder: Disabled Fail Option still triggers inactive branch

Hi,

I have a conditional wait set and a subsequent Delete Files/Folder but with the option “Fail if delete fails” disabled. Still the whole workflow invokes an error state triggering the inactive branch inverter a few component level up the “food chain”.

PS: I will try to replicate the issue in a test workflow.

Edit: Here is the test workflow

Best
Mike

Thanks @mwiegand for the workflow,

I will be trying to reproduce the issue you are having.

TL

2 Likes

Alright so the issue if I am understanding this correctly is that while the node is waiting for the file deletion, and you execute the the top right 2 nodes here:

It will cause the Active Branch Inverter to execute and bypass all the top nodes. I am not able to reproduce it, but it may be because I am on a mac. I can try running this workflow on windows to see if I can encounter it.

TL

1 Like

I wish my two MBPs with display issues were still usable to test if Mac OS has any impact. Another idea what might happen is that the Delete Files/Folders nodes throws a soft error due to the disabled option to completely fail but the Active branch Inverted interferes, interpreting it as a hard error.

1 Like

Hi @mwiegand,

I followed your steps and was not able to recreate the issue. The workflow succeeds without any error on Windows 11.

Best,
Keerthan

1 Like

@thor_landstrom & @k10shetty1 I can confirm the issue is not reproducible in the test workflow anymore.

However, it is still triggered in the original one.

That begs the question, since @thor_landstrom cannot reproduce the issue of the table reader either:

Is there something faulty happening in the originating workflow?

1 Like

Hey @mwiegand,

Yeah it is an intresting issue you have brought up, as for privacy reasons you cannot share the original workflow; I would try running it on a VM if possible to see if it is either machine related or workflow related. If you still get the same error then there is most likely a workflow issue.

Though it seems it will be hard to track down what is causing it. You could try compartmentalizing everything to make sure each every couple nodes run fine and slowly add more until you get to the error again.

Hope this helps,
TL

Hey @thor_landstrom,

indeed it is. Like the two other issues which seem to be reproducible in the originating workflow.

I wonder if there are any temporary settings or temp data that is interfering. Maybe something similar which @takbb and I found in this post?

Best
Mike

1 Like