File Changed Trigger don't works (Serverversion:5.9.6.7)

Server
1

Hi,

i created 2 File Triggers (File appears + File changed)

The file appears works. However, if the task that creates/overwrites the file runs again, the File changed trigger will not be fired, even though the file has a new modification date. Could that still be a bug, or what is the criteria for File Changed trigger?

If i delete/create the File again, File appears is fired again.

regards,

Adrian

3

Thanks for reporting. To figure out what's happening, I need a few details:

Quick questions:

  1. How is the file being updated? What actions/flows are used?
  2. Does it completely overwrite the file or just modify parts of it?
  3. Can you test with Notepad? Open the file, change some text, and save - does this trigger the File Changed event?
  4. Where's the file located? Local drive (C:) or network share (\server)?

Why this matters: We rely on Windows file system events, and they work differently depending on how the file is changed.

  • Complete file replacement : triggers "File Appears"
  • Editing existing content : triggers "File Changed"
  • Network locations** : events can be unreliable

Most likely your flow is replacing the entire file instead of modifying it, which is why you get "File Appears" instead of "File Changed."

what is the criteria for File Changed trigger?

The "File Changed" trigger fires when the Windows file system detects a modification to existing file content.

4

Hello Constantin,

thanks for feedback.
I'm using the Export dataset-Action(Create or overwrite). If exists then overwrite.
The file is located on a network drive.
To test, I simply run the job again a minute later (no changes in the data) The file is created with a new modification date.
But i also edited the DSET and saved it again. However, the trigger is not fired. That's not a big problem.

I changed the project in such a way that the file is deleted after processing. The the appears trigger works.

Regards,

Adrian

5

Hi!

I believe this might be causing the problem. Network drives do not emit all file change events reliably and are not fully supported in this aspect on Windows.

To work around this issue -- if you need the "file changed" trigger -- avoid placing the file on a network drive altogether.

note that mapping the network drive to a local folder (using a hard link or junction) or as a drive will not resolve the underlying Windows limitation.

1 Like
6

Hi,

the file trigger also not fired, if the file is exported to a SAMBA directory via SAP-Program
If the file was copied via Windows file copy, it works (also on sameSAMBA-Network-Drive)
Is the problem known specifically for SAMBA directories?

regards,

Adrian

7

Yes, change notifications on SMB shares is not guaranteed and not supported. It may or may not work

8

Hi,

thanks and .... also "file appears" don't works

regards

Adrian