OpenProject uploads fail when Files Automated Tagging rules are triggered after upgrade to Nextcloud 32.0.6.1

ℹ️ Support
, ,
1

Hi everyone,
we are seeing an issue after upgrading our Nextcloud server to 32.0.6.1.

We use OpenProject 14.6.3 integrated with Nextcloud, and some users reported that uploading attachments from OpenProject was failing.

After multiple tests, we were able to isolate the problem quite clearly:

Environment

  • Nextcloud: 32.0.6.1
  • OpenProject: 14.6.3
  • Nextcloud OpenProject integration app: integration_openproject 2.11.1

Relevant Nextcloud apps enabled:

  • files_automatedtagging 3.0.3
  • workflowengine 2.14.0
  • files_versions 1.25.0
  • admin_audit 1.22.0
  • files_confidential 4.0.0
  • certificate24 0.4.0

What we found

At first, it looked like the issue was related to some specific filenames such as files containing MEMOVAL or MEMOPROC.

However, after more testing, we discovered that the real trigger is:

if an Automated Tagging workflow rule matches the uploaded filename, the upload from OpenProject fails.

This is reproducible even with a very simple test rule.

Minimal reproduction

We created a temporary Files Automated Tagging rule like this:

  • Trigger: File is changed
  • Condition: File name matches /TAGTEST123\.txt/i
  • Action: assign a system tag

Then we uploaded a file from OpenProject named:

TAGTEST123.txt

Result:

  • upload fails

If we disable that automated tagging rule and upload the same file again:

  • upload works

So this does not seem to be related to PDF content, file size, MIME type, etc.
It seems specifically related to Files Automated Tagging being triggered during OpenProject direct upload.

Behaviour observed

  • Files upload correctly from OpenProject when no tagging rule matches
  • Files fail when a tagging rule matches
  • This happens with both .pdf and .txt
  • In some earlier cases, OpenProject reported an error but the file seemed to appear afterwards; in other cases it did not

Logs

The upload requests go through:

/index.php/apps/integration_openproject/direct-upload/...

When the problem happens, we consistently see server-side errors like:

  • OCP\Files\NotFoundException
  • OC\Files\Node\NonExistingFile

And then follow-up errors in other listeners, for example:

  • files_versions: Failed to create version ... node does not exist
  • admin_audit: Exception thrown in file create
  • MetadataUpdate: issue while running MetadataUpdate
  • files_confidential: Failed to tag during NodeWrittenEvent

Code review

We also checked the local code of files_automatedtagging.

It looks like this app is not applying tags on a final node event, but from cache-related events:

  • CacheEntryInsertedEvent
  • CacheEntryUpdatedEvent

This made us suspect there may be some kind of timing issue / race condition with the OpenProject direct upload flow.

Current workaround

As a workaround, we have temporarily disabled the automated tagging rules that affect files uploaded from OpenProject, and uploads are working again.

Question

Has anyone else seen a similar issue with:

  • Nextcloud 32
  • Files Automated Tagging
  • OpenProject integration

Does this look like a known incompatibility or regression?

Thanks in advance.

[/details]

2

Adding link to issue counterpart for the record: Files Automated Tagging breaks OpenProject direct upload on Nextcloud 32.0.6.1 · Issue #1416 · nextcloud/files_automatedtagging · GitHub