issue with the "Dispel" feature in a Conditional Node

[ring4life70]

Hi everyone,

I am facing an issue with the "Dispel" feature in a Conditional Node when monitoring jobs through the FFAStrans WebUI.

In my workflow, I have a Folder Monitor followed by multiple conditional nodes in order to route files to different branches based on their type (Audio, Video, and Documents).

I have checked and enabled the "Dispel" option inside the Conditional node for my "Documents" branch, as I want the node to silently ignore files that do not match the criteria (for example, when a .wav or a .mov file enters the workflow).

However, even with "Dispel" active, every time a non-document file is processed, the WebUI History still reports a red "Error" state for that specific conditional node step, rather than closing the branch silently. This clutters the WebUI dashboard for my team, showing multiple failed rows for a job that actually succeeded on the audio/video branch.

Could you please help me understand why the Dispel function is not preventing the error log in the WebUI history? Am I missing a specific routing logic, or is there a known workaround to achieve a completely silent skip on a branch?

thanks

[momocampo]

Hello Ring4life,
I think, but Emcodem will confim, you should upgrade your webinterface. Could you tell us which version you have please ? This can be indicated in the upper right corner of the web interface.
Thanks

[ring4life70]

hi,
current version on my system is 1.4.0.291
thanks

[momocampo]

Hi,
Ok, and nothing in the inbuilt FFAStrans monitoring status, right ? I mean, no issue about FFAStrans behavior ?
Edit : I tried with the webui V 1.4.0.291 and ok for me, FFAStrans V° is 1.4.1.21)

(you can send me the wf and i will check it out)

[emcodem]

There are some secrets around this, it is actually not that easy to find out for webinterface that the job is dispelled, it must read the log for it instead of just looking at the usual job information from status monitor. However, it should work. I tried 1.4.0.298 (bleeding edge) on ffastrans 1.4.1 and also wasnt able to reproduce quickly. Is it possible for you to reproduce the issue in a way you can easily share the workflow?

[baev12]

Can confirm that every Conditional with %s_source% = "" and "dispel" selected cause Red error stripe (

node error - 1st evaluation of "%s_source% = " is "...long path string"

web ver 1.4.291
other
1.4.1.21
1.4.1.15
1.4.1.26

of course - No Red lines in http://HOST:PORT/monitor (FFAStrans status monitor)

[ring4life70]

Hi, sorry for the late reply. I've attached a workflow that usually triggers an error even though the 'dispel' function is enabled. Specifically, the node named 'DOC' is the one that fails.

[2025] INGEST.json

(37.65 KiB) Downloaded 21 times

[emcodem]

Got that, ok the error was only when there are multiple conditions in the conditional node (more than 3).
I pushed the fix to github, it should automatically create a build this night (later than now): https://github.com/emcodem/ffastrans_webui/releases