I want to apologize for the confusion here. We had an update to the File System connector that has the trigger only return back the metadata of Files. This change was made because some files are too big and the trigger was failing (the On-premises Data Gateway has a relatively low limit for file size).
However, you CAN still accomplish your scenario, it just takes one extra step. Now you can do:
- When a file is created or updated
- Get file content (or, Get file content by path)
- Whatever actions you wanted...
With this pattern you can use an error-handling step to also handle the case where the file is too big, so you can choose what to do (e.g. send yourself a notification, or you could ignore it). That would be impossible with the previous pattern.
Again, sorry for the issue, please let me know if this pattern doesn't work.