Issue

When a Box Relay workflow is set to trigger upon content upload, the workflow does not start even after the user uploads content.

Root Cause

When triggering a Box Relay workflow, the system treats new uploads, moves, and copies as distinct file events.

As a result, depending on the user’s action, the event may not match the trigger conditions, preventing the workflow from starting.

Uploading content to the target folder:

The event is recognized as a new upload. The workflow starts.

Moving content from another folder to the target folder:

The event is recognized as a move operation. The workflow does not start.

Copying content from another folder to the target folder:

The event is recognized as a copy operation. The workflow does not start.

Uploading content to the target folder via Box Drive:

This operation may be treated as a copy in some cases.

In Box Drive, when a file with identical content (same hash value) is re-uploaded after an initial upload, the server copies the first uploaded file instead of re-uploading it to reduce system load.
This makes the event be recognized as a copy operation. The workflow does not start.

Hash values are generated based on file content. If only the file name is changed but the content remains the same, the hash value does not change, and the system treats it as the same file, leading to a copy event.

Resolution

Consider the following changes to operations or settings:

• Upload content directly from a local folder instead of copying or moving it from another folder.

• Modify the workflow to support copy and move events.

• Upload a new file with unique content to avoid being recognized as a copy operation.

Adjust settings based on your environment or circumstances and verify whether the workflow starts as expected.