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


bbusse
2013-04-22T18:00:06Z
Henrik,

I just found something qwirky with an Event Trigger I have configured to look for 'VisualCron--Trigger--Trigger expired (Inactivated)'. I was going to set the up so i'd know if any of my odd file triggers ever get disabled. This definately works, but i noticed something odd.

if I go edit a file trigger on another job, decide not to do anything with it after all, and click OK instead of Cancel, The other job watching for 'inactivated' triggers kicks off. Note, the Active checkbox on the trigger I just edited and re-saved was always checked.

I haven't tried other event triggers to see if they do the same thing when edited and re-saved, but the file trigger does every time you press OK after opening it for editing.

Note: This also happens if I edit a job with a file trigger, go to the Trigers tab, and check the box for 'Reset Trigger dependency state when saving Job'. Not sure what thats supposed to do, but it definately sets off my other job watching for inactivated triggers.

FYI :)

VC: 6.2.1
OS: 2008 R2 w/SP1

I turned on Debugging and edited another job's file trigger, saved it (didn't change anything), and then my 'Test Trigger Disabled notification' job ran.


4/22/2013 1:02:34 PM	Debug	Trigger 'C:\temp\VisualCron_ArchiveTest\*.txt' created, InstanceId: 10 & hashcode: 2402263
4/22/2013 1:02:34 PM	Debug	Next execution (4) for job 'Test Archive and FTP' is: 12:00:00 AM
4/22/2013 1:02:34 PM	Debug	File trigger event (AddHandlers), InstanceId: 10, hashcode: 2402263
4/22/2013 1:02:34 PM	Debug	File watcher started. Directory: C:\temp\VisualCron_ArchiveTest, filter: *.txt, InstanceId: 10, hashcode: 2402263
4/22/2013 1:02:34 PM	Info	Job updated
4/22/2013 1:02:34 PM	Debug	Saving Jobs
4/22/2013 1:02:34 PM	Debug	File trigger event (RemoveHandlers), InstanceId: 9, hashcode: 21523110
4/22/2013 1:02:34 PM	Debug	File trigger event has been ended, trigger: C:\temp\VisualCron_ArchiveTest\*.txt, InstanceId: 9, hashcode: 21523110
4/22/2013 1:02:34 PM	Info	Job started: Test Trigger Disabled notification
4/22/2013 1:02:34 PM	Debug	Job (15) was added to processlist: Test Trigger Disabled notification
4/22/2013 1:02:34 PM	Debug	Next action: ActionContinue
4/22/2013 1:02:34 PM	Debug	Calling GetNextTaskProcess()
4/22/2013 1:02:34 PM	Debug	Next Task is: send mail to bbusse
4/22/2013 1:02:34 PM	Debug	Next action: ActionContinue
4/22/2013 1:02:34 PM	Debug	Calling StartTaskProcess() with Task: send mail to bbusse (0)
4/22/2013 1:02:34 PM	Debug	Task (250) was added to processlist: send mail to bbusse
4/22/2013 1:02:34 PM	Info	Task started: send mail to bbusse (250)
4/22/2013 1:02:34 PM	Debug	Entering wait loop. send mail to bbusse (250)
4/22/2013 1:02:34 PM	Info	Task completed: send mail to bbusse (250)
4/22/2013 1:02:34 PM	Debug	Process status - About to RemoveTaskProcess (250)
4/22/2013 1:02:34 PM	Debug	Setting previous task in TaskProcessCompleted: send mail to bbusse (b87fdfeb-6232-4c91-8cdb-05070cf34d21) in job: Test Trigger Disabled notification
4/22/2013 1:02:34 PM	Debug	Process status - About to SendTaskProcess (250)
4/22/2013 1:02:34 PM	Debug	Process status - About to RemoveTaskProcess (250)
4/22/2013 1:02:34 PM	Debug	Task (250) was removed from processlist: send mail to bbusse
4/22/2013 1:02:34 PM	Debug	Sleep ended because Task ended.send mail to bbusse (250)
4/22/2013 1:02:34 PM	Debug	TaskWaitQueue.Dequeued.send mail to bbusse (250)
4/22/2013 1:02:34 PM	Debug	Else (1)send mail to bbusse (250)
4/22/2013 1:02:34 PM	Debug	End of loop - iterating again.send mail to bbusse (250)
4/22/2013 1:02:34 PM	Debug	Calling GetNextTaskProcess()
4/22/2013 1:02:35 PM	Debug	Job (15) was removed from processlist: Test Trigger Disabled notification
4/22/2013 1:02:35 PM	Debug	Next execution (2) for job 'Test Trigger Disabled notification' is: 12:00:00 AM
4/22/2013 1:02:35 PM	Info	Job completed: Test Trigger Disabled notification




Brian
Sponsor
Forum information
klewis10367
2013-04-22T19:10:00Z
I get the same think...regardless of version.
Support
2013-04-23T07:32:12Z
Currently this is how it is designed. Whenever a Job is being edited (OK clicked) we deactivate all Triggers for that Job and then activate them again. The other trigger is on a lower level and get this deactivation. I am moving this topic to Feature requests to see if we can do something about it in the future.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top