I have been using probes for all my scheduled tasks since moving up to MX. Probes are under tools in CF5, but I don't know if they offer the same functionality.
I realize of course they are probably the same underlying engine - but for some reason, I have not experienced any problem with probes even though they are the same tasks as were not being run as scheduled tasks. Well I have seen one problem - or quirk: probes that I have long since deleted still show up as failing in the MX Application log. I should figure out why, but keeps getting pushed to the back burner given that everything seems to be working fine. -j -----Original Message----- From: Robert Bailey [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 02, 2003 3:51 PM To: CF-Talk Subject: RE: grrrrr ... CFSchedule I have always tested my schedule scripts by having it email me at the end for testing, and executed it with CFSCHEDULE the first time around just to make sure it was completing. Very helpful when you are on a shared host and do not have access to the admin to make sure it was added correctly -----Original Message----- From: Matt Robertson [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 02, 2003 12:48 PM To: CF-Talk Subject: RE: grrrrr ... CFSchedule Howard Owens wrote: <snip> >Any suggestions on why the scheduled events trigger but don't >produce any results? I've always been able to get it to work, but the formula for success has not always been entirely straightforward. This may sound strange at first, but have you tried waiting for 24 hours to see if the thing kicks in? I've had my server monitor running for months on my home-based cf server. Then I had to fiddle with something in cfschedule (I forget what, exactly) for another task and suddenly the thing went dead as a doornail. Couldn't get it to restart despite tinkering with all kinds of stuff. After a bit I gave up and went on to other things, but was very surprised to see it had fired up again the next day, beginning at the start time of the event -- despite the fact that the starting *date* was in the past. I've also had success using '' action="UPDATE" '' in my cfschedule statement. All of the above is for CF 4.5.1sp2. As an aside MX scheduling behaved just fine after an upgrade overtop of cf 4.5x. Shots in the dark, maybe, but who knows... --------------------------------------- Matt Robertson, MSB Designs, Inc. http://mysecretbase.com - Retail http://foohbar.org - ColdFusion Tools --------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
