The best solution is to use the "stop" method from the Workflow Service Rest endpoint. You can simply use it through the Workflow Service Rest documentation (http://localhost:8080/docs.html?path=/workflow). If it still does not work, you can try the "delete" method from the same service.
Xavier On Aug 6, 2012, at 4:54 PM, Rute Santos <[email protected]> wrote: > Hi Xavier, > > Thanks for replying. I am happy to know that this will be fixed soon :) I > am still having problems with it because the operation is re-tried every time > I sanitize the service and I haven't found a way yet to stop it... Is there a > way to completely delete a workflow in process? > Thanks, > > Rute > > > On 8/6/2012 10:18 AM, Xavier Butty wrote: >> Hi Rute, >> >> The functionality you are looking for has been implemented already, and the >> "hold" strategy should indeed put the workflow on hold, offering the >> administrator the possiblity to either retry or discard. Looking at the >> code, it seems that this part of the retry implementation got messed up when >> merging it into 1.4 quite a while ago. Please track MH-9013 for the status >> of this problem. >> >> Here are the answers to your questions: >> >>> 1) If I don't specify max-attempts, will it try the operation forever until >>> the service is fixed? >> >> The default value of max-attemps is 1. But for the hold state strategy, the >> operation will go directly in hold state without trying a second time. >> >>> 2) Shouldn't the workflow stay in on-hold instead of running state? I was >>> expecting to see an admin screen to select the retry strategy for the >>> failed operation. >> >> Yes it should work as described on >> http://opencast.jira.com/wiki/display/MH/Retry+Strategies. You should able >> to choose to select the retry strategy. >> >>> 3) How do I remove it from this state? :) >> >> As described above, the functinoality is currently broken but should soon be >> fixed. >> >> Xavier >> >> >> On Aug 1, 2012, at 5:24 PM, Rute Santos wrote: >> >>> Hi, >>> >>> I defined an operation in a workflow with retry-strategy="hold" and did >>> not specify max-attempts. The operation failed and the workflow remained in >>> RUNNING state. I sanitized the service and the operation failed again (I >>> tried this many times). So my questions are: >>> 1) If I don't specify max-attempts, will it try the operation forever until >>> the service is fixed? >>> 2) Shouldn't the workflow stay in on-hold instead of running state? I was >>> expecting to see an admin screen to select the retry strategy for the >>> failed operation. >>> 3) How do I remove it from this state? :) >>> Thanks, >>> >>> Rute >>> >>> >>> <bfdbfjcj.png> >>> _______________________________________________ >>> Matterhorn-users mailing list >>> [email protected] >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >> >> >> >> _______________________________________________ >> Matterhorn-users mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
