[Bug]: Workflow doesn't even start first action about hop HOT 6 OPEN

what does it say when increasing the log level to debug?

from hop.

I've selected the most verbose log level (row -level - or something - I run the German locale: "Zeilenebene")

It looks like that processing doesn't even get to the point where this can have any effect.

from hop.

Is export linked resources turned on in the remote run configuration? If that is the case I think we will need a reproduction path to further investigate the issue.

from hop.

Yes, Export Linked Resources is checked. However there is no difference at all whether I run the workflow remotely or locally. It just hangs with no clues.

I created a workflow consisting of quite a few simple pipelines - complex SQL in - output to destination table. It worked fine. Then I added a more complex pipeline (containing sorts and a merge) to that workflow and that workflow started to hang. Even removing that complex pipeline didn't help. Copying the structure to a new empty workflow did the job. I could even add the complex pipeline again and it worked. Comparing the xml of the hwf files doesn't show much difference except that the sequence of the piplines is somewhat scrambled.

What can be the cause?

• Memory - we have 6GB in the machine where the GUI resides and 4GB on the server - htop doesn't show memory exhaustion.
• CPU - htop shows that all cores idle
• some strange state - I restarted both GUI and server more than once
• some semaphore or MUX - probably - but how can I find out which one?

I run HOP on an KVM virtual machine running Xfce4. The server is across a VPN at the client's premises. It works so far. It always works when I start a pipeline directly. What's wrong here?

from hop.

Then I think you have found the cause, something must have gone wrong in the workflow file causing it to not load properly.
The error must get eaten up somewhere in the code. It would be great if you happen to still have the broken workflow then we can debug and see where it's going wrong and try to avoid it.

from hop.

Back from vacation - sorry for delay. Meanwhile I'm able to reproduce the issue: I configured a scheduled restart in the Start action. When done so, the Workflow doesn't start. Unckecking the scheduled run option again does not help - the Workflow remains broken. Neither restarting the entire computer nor starting the Workflow and letting it sit there for days changes anything. Deleting and recreating the Start action makes a difference - the Workflow works again.

BTW: the Workflow controls as a whole seem a bit flaky: I could not interrupt a running Workflow properly - it kept continuing despite it recognised the interrupt and there is room for improvement with the schedule configuration in the first place (e.g. graying them out or hiding them when not activated ) making it more transparent what has been configured.

from hop.