Robin Windey

Good catch, thanks for the hint. I think we need to properly recognize this situation and don't throw an error but instead logging an information for example.

Current implementation plan would be like the following: * Add a new switch "Invalidate Digital Signatures" to the per-workflow settings with appropriate help text * If `ocrmypdf` version is <...

Your frontend configuration looks correct. Nevertheless, without additional backend logs it will be impossible to find the error. Like described [here](https://github.com/R0Wi-DEV/workflow_ocr?tab=readme-ov-file#troubleshooting), please decrease your NC loglevel, repeat the process (don't...

There are two interesting lines in your `nextcloud.log`, one is logged by the `workflowengine` itself and the other is logged by this app (`workflow_ocr`): ```json {"reqId":"jiLiFxRBg9xJAAFAsV97","level":0,"time":"2024-01-25T09:32:59+00:00","remoteAddr":"79.249.68.60","user":"daniel","app":"workflowengine","method":"GET","url":"/core/preview?fileId=11909&x=250&y=250","message":"No flow configurations is going...

Some technical details: * The "Flow activation: rules were requested for operation OCR-Datei" log messages is written [here](https://github.com/nextcloud/server/blob/063c051cdcfbaf1f623337f6f1239438b35d094c/apps/workflowengine/lib/Service/RuleMatcher.php#L143) * The "No flow configurations is going to run OCR-Datei" message is...

Seems to be an NC core related issue. Feel free to raise this [here](https://github.com/nextcloud/server/issues). Closed due to lack of feedback.

Confirm that this should be added. We will work on it

Fixed with `v1.28.1`. Added to NC28 only since the version for NC29 already had PHP 8.3 support.

Note: Playwright tests still flaky, t.b. fixed

Thanks for reporting this. Since now the capturing of the exit code works properly, we should take into consideration the different exit codes defined here https://ocrmypdf.readthedocs.io/en/latest/advanced.html#return-code-policy