Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


CeesB
  •  CeesB
  • No customer Topic Starter
2014-09-04T19:33:21Z
Hi,

We have a few jobs that are file trigger based.
All those jobs suffer from the same problem.

When we use an application like Excel or Notepad and use the 'Save As' function and thus save the file in the file trigger directory (Inbox), the job is triggered correct and the file is processed correct.

However immediately after the first run of the job, the job is executed a second time by VisualCron (not simultaneously but after first is finished).

If we save the file first in a temporary directory and then copy the file to the file trigger directory the job is triggered and processed only once.

We are currently on version 7.1.6 but have the same problem in our older version 6.2.1.

Why is the file trigger event in VisualCron treated differently when:
a. creating it through a 'Save As' function in an application (job is executed 2x)
b. copying it from another directory (job is executed 1x, which is correct).

Kind regards,
Cees
Sponsor
Forum information
ErikC
2014-09-05T06:36:09Z
Hoi Cees (Hoi = dutch for Hi)

Could you tell us what your trigger flags are? Default it looks at creation an towards the filename.
It could be that the 'save as' method saves the file (create trigger) and than renames the file (filename trigger) so it will fire twice.
If you copy a file in a directory only the file create trigger will fire.

You can check this by looking at the trigger variables. Output the trigger filename {TRIGGER(Active|LastTrigger|File.Result.Name)} than you know for sure.

Regards,
Erik
Uses Visualcron since 2006.
CeesB
  •  CeesB
  • No customer Topic Starter
2014-09-05T15:05:48Z
Hoi Erik,

Thanks for your reply.

I have been checking all trigger variables and came to the conclusion that setting the 'Duplicate file delay' to 3000 miliseconds (default usually 300) solved the problem. Maybe setting the number lower than 3000 could also help, but what is 3 seconds in a man's life :-)

Your remark about the two possible steps (create trigger and filename trigger) that could fire it twice put me to that solution. It was most helpful, thanks!

Kind regards,
Cees
Scroll to Top