nextcloud / nextcloud/workflow_script

"File created" flow rule stops triggering after container restart

Aperta
#486 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Lingua principale
PHP
Stelle
89
Fork
19
Merge medio
6h 38m
PR unite (30g)
3

Descrizione

"File created" flow rule stops triggering after container restart (v3.0.0, Nextcloud AIO)
Description
The "Run script" flow with a "File created" trigger stops firing after a Nextcloud AIO container update/restart. The rule appears active in the UI but never triggers, even for files uploaded through the Nextcloud web interface.

Environment
Nextcloud version: 32.0.4.1
workflow_script version: 3.0.0
workflowengine version: 2.14.0
Installation: Nextcloud AIO (Docker)
Steps to Reproduce
Create a flow rule:
When: File created
and: File name matches /daily\d{4}-\d{2}-\d{2}_.*.gpx$/i
Run script: python3 /opt/phonetrack_timeline_updater.py --file "%f" --path "%n"
Rule works correctly after initial setup
Nextcloud AIO container is updated/restarted
Rule still shows as Active in Admin → Flow
Upload a file matching the pattern through the Nextcloud web UI
Script is never executed — no log entries, no side effects
Expected Behavior
The script should be triggered when a matching file is uploaded, even after a container restart. The rule is displayed as "Active" and should behave accordingly.

Actual Behavior
The rule silently stops working. No errors in nextcloud.log, no indication that the flow engine is attempting to run the script. Deleting and recreating the rule does not fix the issue.

Troubleshooting Done
✅ Confirmed workflow_script app is enabled (php occ app:list)
✅ Confirmed script exists and is executable at /opt/phonetrack_timeline_updater.py
✅ Script works correctly when run manually
✅ Deleted and recreated the flow rule — still doesn't trigger
✅ Uploaded test file through Nextcloud web UI (not filesystem) — still doesn't trigger
✅ No relevant errors in nextcloud.log
✅ Nextcloud cron is running (other background jobs work fine)
Notes
The rule worked reliably for about a week after initial setup (Jan 17–24, 2026)
After the container was updated, the rule stopped working permanently
This may be related to #65 and #90

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia esaminando il comportamento di workflow_script relativo al trigger File created e ai report correlati #65 e #90. Riproduci il malfunzionamento dopo il riavvio di un container Nextcloud AIO, utilizzando la regola Admin → Flow, php occ app status e i controlli di nextcloud.log descritti qui. Il lavoro è completato quando la regola attiva esistente esegue lo script configurato per i file corrispondenti caricati tramite il Web dopo il riavvio, con un test di regressione o una verifica documentata.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
docker, php
Ambito
backend
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.