Scheduled Task Suggestions

1. Is this happening recently? We updated the backend service about a week ago that should have fixed that.

2. We do not capture the status code because the service will need to wait for the script to complete. Sometime script can run for a long time (~90 seconds)

3. Disable feature is already being considered and will be available.

quote:Originally posted by homeacademy

I've been testing your scheduled task feature. I'm very pleased you have begun offering this. I do have a couple of questions/suggestions though:

* The scheduled task I have running is a ASP.NET app which simply copies around some files on my account. I have been looking at the timestamp on the copied files in Frontpage and can't understand what I'm seeing. I have my task set to run at Daily at 04:00 PST, and I have not been changing that setting. However, the timestamps on the resulting files are erradic. Some at 2:02 PM, 8:31 AM, 5:32 PM, and lots of other stuff. I would expect it to be at 4:00 AM every time? Am I missing something?

* I would really like to see some better logging and results for each time the task runs. I used www.script-schedule.com for some of my scheduling needs before you began to offer this feature, and I think their interface is really well designed. At a glance, I can see the HTTP Status Codes for the last 5 times a particular scheduled task ran. I can click on any one of those, and a new window opens displaying the complete browser output (resulting page) created when that task ran. It makes it easy to see exactly what happened when the task ran (and to troubleshoot any problems). Perhaps DiscountASP could take a look at the script-schedule interface and emulate some of the features. It would really make your Scheduled Task feature more powerful and useful.

* This doesn't really apply until after the beta period when we have multiple scheduled tasks, but I would really like an easy way to disable/enable particular tasks without deleting and recreating them. Maybe a simple check box next to each task to control the enabling/disabling?

I think that's it (at least for now []). Thanks again for introducting this feature. Let me know what you think.
</blockquote id="quote"></font id="quote">

 

1) pls create a support ticket. the sa can review the log to see when your task was ran.

2) getting the http output means that we have to wait for each page to complete execution. we'll eventually fix this by changing the scheduler service to a thread based service but it's going to take sometime because of the complexity.


quote:Originally posted by homeacademy

1. Yes, it has been happening since you released the scheduler service, and is still occuring. If you want, I will set up an app to just log the timestamp to a database each time it is run and schedule that so we can see exactly what is happening. I have not tried anything other than a daily schedule, I don't know how it is for say the 15 min schedule but I can test that too. If you want me to, just let me know.

2. Okay, the status code isn't that big a deal. But I really would like to view the browser output for a script. Possible?

3. Wonderful!
</blockquote id="quote"></font id="quote">