nextcloud / nextcloud/workflow_script

"File created" flow rule stops triggering after container restart

Abierto
#486 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
PHP
Estrellas
89
Forks
19
Merge medio
6 h 38 min
PR fusionados (30 d)
3

Descripción

"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

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Empieza revisando el comportamiento de workflow_script en torno al disparador File created y los informes relacionados #65 y #90. Reproduce el fallo después de reiniciar un contenedor de Nextcloud AIO, utilizando la regla Admin → Flow, php occ app status y las comprobaciones de nextcloud.log descritas aquí. Se considera terminado cuando la regla activa existente ejecuta el script configurado para los archivos coincidentes subidos mediante la web después del reinicio, con una prueba de regresión o una verificación documentada.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
docker, php
Área
backend
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
45/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.