This is correct. If you cancel a service before it runs, the next
instance will not run and prevent the service from being rescheduled.
Simply issuing a cancel on a job is the best and easiest way to do this.
The other way is to set the end date on the recurrence. At this
moment there is no UI for this, so you will have to edit this in the
recurrence tables.
Andy
On Jul 16, 2006, at 1:48 AM, Pradeep Sharma wrote:
I think this can be done easily from webtools by just clicking on
cancle
button of the scheduled service. I am not sure but I guess I have
done this
before.
Thanks,
Pradeep Sharma
On 7/15/06, Brett Palmer <[EMAIL PROTECTED]> wrote:
Al,
I don't think just changing the finishDateTime or the statusId will
stop a scheduled service from running. I've tried those techniques
before and the services continue to run. I think you need to change
the recurrenceInfo data to kill a scheduled service. This is
something Andy could probably answer best. One of these days I'm
going to take the time to figure out how to do this and put it in the
wiki.
Does anyone have a good formula for stopping services in the
job_sandbox?
Brett
On 7/15/06, Al Byers <[EMAIL PROTECTED]> wrote:
> I am just looking into service scheduling and I see plenty for
> scheduling a long running, recurring service, but nothing for
> terminating that scheduled activity. Is it just a matter of
finding that
> JobSandbox record and modifying the finishDateTime?
>
> -Al
>
