tag:blogger.com,1999:blog-4061740313877866897.post7851227608902505198..comments2011-12-12T09:05:11.730+11:00Matt Laceyhttps://profiles.google.com/111827922894049648255noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4061740313877866897.post-54335766095339678072011-12-12T09:05:11.730+11:002011-12-12T09:05:11.730+11:00I've threatened to do this myself on numerous occasions, unfortunately it's always been one of those stupid things where I go for the ten minutes of manual work instead of the thirty of coding, though usually because I need to get something deployed quickly. Kudos to your colleague!Matt Laceyhttp://www.blogger.com/profile/07254148667338147404noreply@blogger.comtag:blogger.com,1999:blog-4061740313877866897.post-5285533472658353912011-12-12T02:39:38.988+11:002011-12-12T02:39:38.988+11:00One of the developers I work with grew so tired of this he wrote a little visual force page where each job was listed with an on/off button and it's current status listed. He could then see at any moment the status of each of the normal batches and toggle them off/on at will.Robhttp://www.blogger.com/profile/06586356025825975334noreply@blogger.com