I initially thought that you could use the automation filter to filter out any message for paths that are not the root gdb - ending in ‘.gdb’. However the filter only looks to run a ‘contains’ check, so that approach doesn’t work.
The approach I then came up with was to run your space for every create call. The very first thing you workspace does is checks the value that is passed from the automation. If it is not the root of the GDB, then do not continue the process.
Its not an ideal approach as it does mean you will then call that work space many times and only one of the calls will actually do anything.
I do note there is this idea to support regex in the automation Filter:
One thing to also keep in mind with this workflow is that the .gdb folder is created first; before any of the underlying files. You do run the risk of triggering your workspace before the gdb is fully copied/created
Thanks @hkingsbury, RegEx would indeed be nice here, thanks for the link. I’ll give your suggestion a try.