Task Schedular sends more frequent emails than interval
I am on umbraco v6.1.1. I've installed the package and changed upbracoSettings.config to run a task every 7 days (once a week). The url by itself executes fine and sends an email when run.
So what you did is use Taskscheduler and you've also added the url by itself in taskname? In UrlScheduler there is a check for the time but that's not in the normal Umbraco scheduled task(that you configured in the config file) which will propably execute after a .net application pool reset and therefore the task is executed every day. My suggestion is to remove the task from config and only execute it via TaskScheduler.
I tried executing the task just via TaskScheduler - but that doesn't run at all. When you say via TaskScheduler, you mean creating a node in developer and set the values for duration and url, right? Here's what I did. (This doesn't run for any duration, Hour, Day, Week)
In this TEST case, I am checking if scheduled task runs every hour (right now it's not running at all). If this is successful, in the PRODUCTION case, I actually need it run once every week. Is that clear?
No sorry not a clue. Maybe the site is not active at the moment it needs to run (app_pool shutdown) or similar. I've solved a similar issue in CMSImport that it still executes when the application is restarted. I should port that to task scheduler also but time is limited at the moment.
Thanks for all the help Richard. Deploying the task scheduler on a live website - that's active - works just fine. The test server doesn't provide an accurate test.
Task Schedular sends more frequent emails than interval
I am on umbraco v6.1.1. I've installed the package and changed upbracoSettings.config to run a task every 7 days (once a week). The url by itself executes fine and sends an email when run.
The problem is that with the above config change, the email is fired once every day, instead of once every week.
If I setup the same from CMS 'Task Scheduler' node (by creating a child node under Week and provide a url), the email isn't fired at all.
Is there anything missing here?
Hi,
So what you did is use Taskscheduler and you've also added the url by itself in taskname? In UrlScheduler there is a check for the time but that's not in the normal Umbraco scheduled task(that you configured in the config file) which will propably execute after a .net application pool reset and therefore the task is executed every day. My suggestion is to remove the task from config and only execute it via TaskScheduler.
Cheers,
Richard
Hi Richard, thanks for prompt response.
I tried executing the task just via TaskScheduler - but that doesn't run at all. When you say via TaskScheduler, you mean creating a node in developer and set the values for duration and url, right? Here's what I did. (This doesn't run for any duration, Hour, Day, Week)
Yes I mean that it could be that it doesn't run becvause the interval needs to be 1 minute.
Let me try that. Adding the following in config (1 miunte interval) and keeping the task url as shown in image above (1 hour interval).
Hmm, no luck Richard. No email is fired - any more clue?
And the time is set correctly, as in within the same time period as the test?
Yes, time is set correctly. There're just two settings as per what you suggested. Let me repeat them here.
1) umbracoSettings.config
2) Scheduled Task in Developer section :
In this TEST case, I am checking if scheduled task runs every hour (right now it's not running at all). If this is successful, in the PRODUCTION case, I actually need it run once every week. Is that clear?
Hi Richard, any clue on this? A production release is waiting on this...thanks
Hi,
No sorry not a clue. Maybe the site is not active at the moment it needs to run (app_pool shutdown) or similar. I've solved a similar issue in CMSImport that it still executes when the application is restarted. I should port that to task scheduler also but time is limited at the moment.
Best,
Richard
Thanks for all the help Richard. Deploying the task scheduler on a live website - that's active - works just fine. The test server doesn't provide an accurate test.
is working on a reply...