The file watch should fire when any of the above said file types are available.

Thanks

Last edited by jambai on Tue Mar 19, 2013 11:51 am; edited 1 time in total

Mon Mar 18, 2013 11:18 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6754

The path seems to be correct. Not sure what to make out of this case.

Since all files are in one place, one the things you can do is to use a common file mask \\fs-uc-1\TW\CP\BC-Del\*.* to catch all 3 file types at once
and then using JavaScript or other script type job move only jpg, jpeg, or zip file

This wouldn't heart even if a file with different extension get created in the same directory.

Mon Mar 18, 2013 10:00 pm

jambai

Joined: 14 Feb 2013Posts: 22Country: United States

File watch on multiple semaphores

If I give the common file mask, the task runs every minutes of what I gave under "How often do you want to check for these files?.

The task triggered even though there is no files were placed in that directory. It is running

Thanks

Tue Mar 19, 2013 11:51 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6754

Which means the directory is not empty, right?
Can you clean up that directory?
Delete files with unneeded extensions?

Tue Mar 19, 2013 12:52 pm

jambai

Joined: 14 Feb 2013Posts: 22Country: United States

File watch on multiple semaphores

It doesn't matter whether the directory is empty or not empty, the job triggers.

Thanks

Tue Mar 19, 2013 2:19 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6754

Code:

It doesn't matter whether the directory is empty or not empty, the job triggers.

i'm unable to reproduce that issue.

Are there any sub-folders in \\server\directory\files ?

Quote:

When I set up a file watch job on a semaphore file (\\server\directory\files\*.jpg), the job fires fine.
It is not working when I add multiple files (\\server\directory\files\*.jpg, \\server\directory\files\*.jpeg) on the file watch.

I'm able to reproduce this one. Seems like a regression to me. I've reported that case to our internal support system.

Would you please describe again which issue you are talking about? use of multiple file masks in the job file-watch trigger or something else?

Last edited by SysOp on Sat Mar 23, 2013 4:05 pm; edited 1 time in total

Sat Mar 23, 2013 10:55 am

jambai

Joined: 14 Feb 2013Posts: 22Country: United States

File watch on multiple semaphores

Use of multiple file masks in the job file-watch trigger

Thanks

Sat Mar 23, 2013 2:23 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6754

The given code is for the job script. It is not related to the job trigger, that is the code that job would run if triggered. The only solution for the moment is to use a single catch-all semaphore file mask, and then in the job handle the details.

As a follow up to my previous note that I've reported the issue with using multiple semaphore file masks to our development team - that issue is going to be fixed in the next build expected sometime next week.