You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Save it in a location where nextcloud can access it and make it executable.
As nextcloud admin create a new run_script workflow that triggers on pretty much any event.
Save the workflow.
Create a file named foo.txt.
Change the contents of the file by editing via nextcloud webinterface.
Change the contents of the file by locally editing the file via sync-client.
Assign a tag to foo.txt
touch the file on a synched client.
Delete foo.txt via Webinterface or sync-client
Test with different regular expressions, make sure to only use lower-case ASCII characters in filenames so we can be sure that nextcloud doesn't trip over any “special characters”.
filename matches /^foo\.txt$/i (as in the example given by the web interface when creating a flow)
filename matches foo\.txt (same as above but not case insensitive, though our testfile is explicitly lowercase only)
filename matches foo.txt (With . as a wildcard, no dice)
filename isfoo.txt (Explicit and literal exact filename.)
filename matches foo.* (to match anything beginning with foo…)
filename matches .* (Doesn't trigger as well though we'd expect this one to trigger on literally any file since that matches everything.)
Expected behaviour
Upon change of a file named foo.txt the run_script flow should be triggered and successfully executed.
To be honest, we never go this to work at all since run_script was introduced. So this is not a recent regression from our point of view, it never worked.
Nextcloud Version: (see admin page)
Versions prior to Nextcloud 17 not relevant anymore, but didn't work there as well.
18.x.y
19.x.y
20.0.3-20.0.0
21.0.0-21.0.1
Where did you install Nextcloud from:
Debian package
FreeBSD package
Source
Signing status:
Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.
Result on all Instances this was tested on: No errors have been found.
List of activated apps:
```
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your server installation folder
```
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
Are you using external storage, if yes which one: local/smb/sftp/...
Local storage only.
Are you using encryption: yes/no
Nextcloud E2EE: No.
TLS: Yes
Server log (data/nextcloud.log)
nextcloud.log doesn't log any events. flow.log is constantly at 0 bytes no matter if flows are triggered (for example the “Automated tagging” flow) or run_script doesn't trigger.
Additional remarks
I've made sure that the script to be executed is not located within a group folder because of #38.
Testing the flow trigger system with “Automated tagging” does work to auto-add a tag upon change of a file. So we're really certain that all of these nextcloud installations are generally ok and they've been working fine otherwise.
Edit
Added info on nextcloud.log and flow.log.
Added another PHP version
Clarified trigger configurations for filename matches and filename is.
The text was updated successfully, but these errors were encountered:
Background jobs are run via cron(8) have been and are working perfectly fine. There have been no changes to the cron(8) jobs at all. I've tried loglevels from 3 to 6. I'll check if setting it to 1 makes any difference.
Steps to reproduce
Save it in a location where nextcloud can access it and make it executable.
foo.txt
.foo.txt
touch
the file on a synched client.foo.txt
via Webinterface or sync-clientTest with different regular expressions, make sure to only use lower-case ASCII characters in filenames so we can be sure that nextcloud doesn't trip over any “special characters”.
/^foo\.txt$/i
(as in the example given by the web interface when creating a flow)foo\.txt
(same as above but not case insensitive, though our testfile is explicitly lowercase only)foo.txt
(With.
as a wildcard, no dice)foo.txt
(Explicit and literal exact filename.)foo.*
(to match anything beginning with foo…).*
(Doesn't trigger as well though we'd expect this one to trigger on literally any file since that matches everything.)Expected behaviour
Upon change of a file named
foo.txt
the run_script flow should be triggered and successfully executed.Actual behaviour
Nothing.
Workflow Script app
Workflow Script app version: (see apps admin page:
/index.php/settings/apps
)Multiple Nextcloud 20.0.9.1: Workflow external scripts: 1.5.1
Nextcloud 21.0.1: Workflow external scripts: 1.5.0
To be honest, we never go this to work at all since run_script was introduced. So this is not a recent regression from our point of view, it never worked.
Server configuration
Operating system:
FreeBSD 12.2-RELEASE-p6
Debian 10 (Buster)
Web server: Apache/Nginx
nginx 1.20.0
nginx 1.19.x
nginx 1.18.x
nginx 1.14.2
Database: MySQL/Maria/SQLite/PostgreSQL
MySQL 5.7.33
Postgres 13.2
MariaDB 10.3.27
PHP version:
PHP 7.4.18
PHP 7.4.16
PHP 7.3.27-1~deb10u1
PHP 7.3.x
PHP 7.2.x
Nextcloud Version: (see admin page)
Versions prior to Nextcloud 17 not relevant anymore, but didn't work there as well.
18.x.y
19.x.y
20.0.3-20.0.0
21.0.0-21.0.1
Where did you install Nextcloud from:
Debian package
FreeBSD package
Source
Signing status:
Result on all Instances this was tested on:
No errors have been found.
List of activated apps:
Nextcloud 20.0.9
Nextcloud 21.0.1
Nextcloud 20.0.9.1
Nextcloud configuration:
Nextcloud 21.0.1
Nextcloud 20.0.9.1
Another Nextcloud 20.0.9.1
Are you using external storage, if yes which one: local/smb/sftp/...
Local storage only.
Are you using encryption: yes/no
Nextcloud E2EE: No.
TLS: Yes
Server log (data/nextcloud.log)
nextcloud.log
doesn't log any events.flow.log
is constantly at0
bytes no matter if flows are triggered (for example the “Automated tagging” flow) orrun_script
doesn't trigger.Additional remarks
I've made sure that the script to be executed is not located within a group folder because of #38.
Testing the flow trigger system with “Automated tagging” does work to auto-add a tag upon change of a file. So we're really certain that all of these nextcloud installations are generally ok and they've been working fine otherwise.
Edit
nextcloud.log
andflow.log
.The text was updated successfully, but these errors were encountered: