- Nextcloud Server version (eg, 29.xx): 30.0.4.1
- Operating system and version (eg, Ubuntu 24.04): Ubuntu 24.04
- Web server and version (eg, Apache 2.4.25): Apache/2.4.62 (Debian)
- Reverse proxy and version (eg nginx 1.27.2): nginx 1.27.2
- PHP version (eg, 8.3): 8.2.27
- Is this the first time you’ve seen this error? (Yes/No): Yes
- When did this problem seem to first start? When testing workflow automation with folder tagging.
- Installation method (eg AlO, NCP, Bare Metal/Archive, etc.): Docker
- Are you using Cloudflare, mod_security, or similar? (Yes / No): No , Caddy
Summary of the Issue
The Flow app (workflow engine) does not trigger the external script function when a folder is tagged, even though the tagging event is logged. However, when a file is tagged, the external script is triggered without any issues.
Steps to Replicate
- Create or upload a file or folder to Nextcloud.
- Apply a system tag to the file or folder.
- Monitor the logs for the workflowengine app to observe behavior differences between file and folder tags.
Observations
-
For files:
- The Flow app logs the event (
OCP\SystemTag\ISystemTagObjectMapper::assignTags
) and successfully triggers the external script. - Example log entry:
Flow rule qualified to run Run script, config: {"operation":"python3 /scripts/flow_tag_notify.py ..."}
- The Flow app logs the event (
-
For folders:
- The Flow app logs the tagging event but does not trigger the external script.
- Example log entry:
Flow activated by event OCP\SystemTag\ISystemTagObjectMapper::assignTags
-
The workflow engine seems to treat folders differently from files, and no rules are applied for folders, even though the tag assignment is recorded.
Nextcloud Log Entries
File Tag Log:
{"reqId":"hLz5DQotPEdRcJukkTRz","level":0,"time":"2025-01-10T05:25:14+00:00","remoteAddr":"10.0.0.84","user":"NCAdmin","app":"workflowengine","method":"PUT","url":"/remote.php/dav/systemtags-relations/files/1635489/24","message":"Flow rule qualified to run Run script, config: {"operation":"python3 /scripts/flow_tag_notify.py ..."}"}
Folder Tag Log:
{"reqId":"gKvQTkqVlVUXzzeyEtO7","level":0,"time":"2025-01-10T05:21:39+00:00","remoteAddr":"10.0.0.84","user":"NCAdmin","app":"workflowengine","method":"PUT","url":"/remote.php/dav/systemtags-relations/files/1632491/24","message":"Flow activated by event OCP\SystemTag\ISystemTagObjectMapper::assignTags"}
Configuration
Nextcloud config.php:
Click to expand
{
"htaccess.RewriteBase": "/",
"memcache.local": "\\OC\\Memcache\\APCu",
"apps_paths": [
{
"path": "/var/www/html/apps",
"url": "/apps",
"writable": false
},
{
"path": "/var/www/html/custom_apps",
"url": "/custom_apps",
"writable": true
}
],
"redis": {
"host": "***REMOVED SENSITIVE VALUE***",
"password": "***REMOVED SENSITIVE VALUE***",
"port": 6379
},
"dbtype": "mysql",
"version": "30.0.4.1",
"installed": true,
"loglevel": 0
}
Questions
- Does the Flow app support folder tagging events for workflows?
- Is this behavior expected or a known issue?
- Are there any workarounds or configurations to make the Flow app trigger external scripts for folder tags, as it does for file tags?
- Could this require custom modifications or additional logging to detect folder-related triggers?
Additional Context
- Below are the relevant app versions:
- workflowengine: 2.12.0
- workflow_script: 1.15.0
What I’m Looking For
I would greatly appreciate any guidance, workarounds, or fixes for this issue. If this is a limitation of the Flow app or Nextcloud, suggestions for custom development or reporting this issue to the developers would also be helpful.
Thanks for your support!
Best regards,
Daniel