AWI: End file event after a maximum time and send email notification at time prior to Maximum time reached

[Luna Dunham]

Hello! Any help with this would be appreciated. I am currently having an issue with setting up an event file within the Automic Web Interface. 

I have an Event file, EF. I want to end EF after a set time. For instance, if it is passed 22:00, EF is canceled. I also have a unix job, File Watcher (FW). FW is set to get information and pass it on to an email notification. I am want to activate FW after a specific time.  So for example, if it is 10:00, FW is activated. 

I am having trouble setting EF up so that it will monitor both times to end the task and send the email. I have looked at the Maximum runtime (General -> runtime) to stop at 22:00. And looked in the process. I have looked at monitoring both min and max runtime, where I send the email on minimum runtime -- I have had issues where it immediately activates FW. 

I am scratching my head as to how to configure this. Any advice would be appreciated. 

Thanks.

[Jared Kessans]

If I am understanding this correctly, you should be able to have your MRT on the EF set for a specific time, then without quitting the EF but trigger in the FW.  Then as part of the FW, you should do your process and then use CANCEL_UC_OBJECT to quit the EF.  You should be able to retrieve the the EF run number using ":READ &UC_CAUSE_NR,," as part of your FW job.

[Luna Dunham]

I am looking to have them run independently of each other. So If is past 10:00, FW is triggered but EF still runs until its MRT is reached at 22:00. If the check frequency is set to be in intervals, would it run Event process or process every interval? Because one solution could be to check the sys_time and if its passed FW's time, trigger it. But I am also worried about it triggering multiple times.

[Jared Kessans]

By EF, I am assuming that you are referring to a File Event which is used specifically to monitor a path for the existence of a file.  When executing the File Event, it will run any script on the Process tab.  When a file is found, it will then run the Event Process tab.  During those checks while no file is found no UC4 script is processed.

You can use the Process tab (ran at activation) to trigger in the FW with a start time of 10:00, then still use the MRT to quit the File Event at 22:00?

[Luna Dunham]

I see. Where i currently am: the file event triggers the FW (which is now a workflow, cause it allows me to choose a specific start time) at the beginning of the process. Next I am working on having the file event cancel FW if the file is detected. 

This feels a little off from the first comment you made, but I ultimately don't want to cancel the file event and hope to cancel the watcher if the event process is started.