Workflow not being run about workflow_script

[blizzz]

I have the fix: #10. It's rather embarrassing and i have no explanation how it slipped in first place :-/

[it25fg]

Hopefully this won't open the issue again... Simply want to confirm that my flavor of the issue (workflow not being run on upload or on modification via sync client) really has gone away. Many thanks @blizzz & keep up the good work!

[blizzz]

A cronjob should be registered, the scripts are executed with a background job.

[kgw4it]

Hey. Thanks for the quick reply. I checked the oc_jobs table and I never saw an entry there that looked like it's related to the workflow_script app.
As far as I understand, here https://github.com/nextcloud/workflow_script/blob/master/lib/AppInfo/Application.php#L73 listeners are registered to execute in case a file gets added or updated or renamed. Therefore for every file I upload I would expect that this line https://github.com/nextcloud/workflow_script/blob/master/lib/AppInfo/Application.php#L44 is executed. But my debugging showed that this code only gets executed for previews that are generated after a file was uploaded, but never for the file itself.
That's why I assumed that something is wrong with the hooks..

Just to confirm setting up a single rule group without any rules and the following command echo "%e %i %a %o %n %f %x" >> /tmp/1.log, should in fact add a line to the /tmp/1.log file every time a file gets uploaded, right?

[blizzz]

I share your expectations.

Just to confirm setting up a single rule group without any rules and the following command echo "%e %i %a %o %n %f %x" >> /tmp/1.log, should in fact add a line to the /tmp/1.log file every time a file gets uploaded, right?

Yes, however on systemd-based systems /tmp/ is usually jailed on a service subdirectory on /tmp, e.g. /tmp/systemd-private-3f055192b6d41929609a65440ab0fbc-httpd.service-95Rog0/tmp

[idistech]

Im seeing the same behaviour here - Ubuntu 16.04 - Ive placed the script and the output to /var/tmp and /var/www and /var/log/nextcloud but getting the same issue - is there somewhere were we can see an error log to you think ?

[blizzz]

@idistech it must also have permission to write to those directories. if something is logged, then in the nextcloud log file within the data directory.

[chasx003]

I'm having the same issues. I don't see any logs that even make me think the script is trying to run. Just trying to echo to a location that www-data owns.

Seems this person is also having the same issues https://help.nextcloud.com/t/help-with-workflow-external-scripts-app/47937

[wiswedel]

(almost) same for me. Script is only being triggerd on creation of a new text file from the web UI. Uploads, renamings, folder creation etc. aren't triggering anything.

[it25fg]

Same here. The only event that causes a script to be executed is content modification. No exceptions in the log.
Besides, even content modification does not always trigger anything, for instance if the ruleset contains rules mentioning tags. I have created nextcloud/server#14401 for this as it seems to be a problem in the workflow framework.

[blizzz]

I gave it a try as well, and yes there seem to be some issue, alas specific to checks. It worked for me when i restricted the user to be part of a group. This worked. What didn't:
mimetype – was interpreted as "application/octet-strem" instead of "plain/text"
tag – could not resolve the path to file ids

What are your failing rules?

[it25fg]

Nice to meet you @blizzz

What are your failing rules?

First, I tested a simple rule 'file has tag' that never fired because of an exception in the workflow framework. Then, I found one rule that worked: this was a file name regexp. Later on, I noticed that even this was only fired on modification from the web frontend. Not on upload, and not on modification on a watched directory in a desktop client. That's all I've seen so far, I'll continue testing.

[blizzz]

Heyo @it25fg :)

thanks for the input, I'll investigate that, too!

[wiswedel]

My rules were file name regexp and no rule at all which usually fires for every object everytime something happens (at least that's how files_automatictagging reacts)

[blizzz]

i published the 1.0.1 with the fix

[blizzz]

Thanks @it25fg for confirming and the nice words :)

[orangeswim]

hello, i see that this issue is already closed, but i'm running into the same issue.
Workflow external scripts 1.1.0
NextCloud 16.0.1

[blizzz]

@orangeswim please open a new bug report with all requested details