Ongoing saga of the Chad CFSchedule CFPop Learning Curve
Here's my non-best practice background, to avoid assumptions. ;)
Initially, I did the following cfschedule:
<cfschedule
action="update"
task="MyTaskName"
operation="HTTPRequest"
startdate="27/2/05"
starttime="10:00 AM"
URL="http://www.myurl.com.au/prism/mycfmpage.cfm";
interval="60">
Had some problems, where the task was for some reason set to start at
the year 2057. Also, 60 seconds didn't work, but 120 seconds did.
So we got it working.
The page it calls is a simple cfpop, followed by a cfloop through the
cfpop query.
But then the server encountered this:
"Error","1160","03/02/05","14:46:13",,"Status code for task:
'MyTaskName' is '500 Internal Server Error'"
But when I manually ran the page it was fine. Problem is that it reset
the scheduled task to starting in 2057 and 60 seconds! So my questions:
1. Why would it reset it?; and
2. Will a cfpop chuck a 500 error if it fails to connect to the pop
account? (only reason why I figure it would error, but then work fine
when I manually ran the page later)
Thanks!
Chad
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
