We were recently alerted to a "failure" with a file event in our v12.3.5 environment. (Yes, I know it's v12. We're working to get everything migrated up to v24 at the moment.)
The (linux) file event sits within a workflow and is configured to look for 'Number of files >= 1' with a frequency of 'Once', and the Event Process tab is configured to activate a separate workflow for each file it finds.
In this particular case, the event shows as successful, but there's no !Event child task, and the event's Logging report shows this:
2024-09-27 09:52:09 - U02000102 Error when calling the function 'lstat64', error code '2(No such file or directory)'.
2024-09-27 09:52:09 - U00011166 System message: ''
This happened despite the folder actually existing and there being files present in it. (There was actually a parallel instance of this same event running a separate workflow and looking in the same folder but for a different filename pattern. That instance worked just fine.)
I was disappointed to see that there was no failure registered anywhere when this happened -- the event itself was still ENDED_OK, and there was no !Event triggered, because the event didn't seem to find the folder.
Has anyone else run into this kind of problem?
If so, have you figured out a way to trap for this kind of error? (I did reach out to Broadcom support, but they haven't been helping because v12 is no longer supported; they invited me to try to reproduce the problem in v24.)
-- Daryl