Posted by hujia on October 8, 2009 at 4:27pm
Jump to:
| Project: | Workflow |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I set up my workflow and it works really well. However, the schedule for state change, which I used for publishing, doesn't work at all. eg at 09:30 am I set it at "09:50" and wait for the item to publish and it never happens. is the time format wrong (i used HH:MM)... or I need to set it up somewhere that I missed? (to me schedule is a not really needed optional, but it would be a nice to have if it works).
By the way, the state works per se for publishing content. thanks! Huj
Comments
#1
Scheduler needs cron to run. Didn't you forget it?
#2
Thanks for your reminder: I thought by scheduler, like MS scheduler it is scheduler that means what it is supposed to mean, a trigger for event to happen at a point of time: no? so if either I use unix or ms scheduler to crontab it, then why do i still need this scheduler here?! I don't get it: since either can set time triggered event down to the second and with repetitions at discretion... Huj
#3
Hi,
This ticket was last updated over 1 year ago, and hasn't seen a reply since then. Based on that, and that development is now progressing on Drupal 7, I'm going to go ahead and close this one out. If you would still like to see this issue addressed, please post a request for Drupal 7, then we can work on the Drupal 6 version.
- Bastlynn
Scheduling a transition puts the job in a queue to be done on cron - even MS scheduler is still putting things in a to-do list before executing them at a regular set time when some internal to the OS event (usually the clock time) tells it to go look at the to-do list. So please remember to run cron on your website to cue the website to do all the fun things you've scheduled it to do. Computers don't act on their own without something to tell them to act.