On Friday, March 29, 2013 9:14:41 PM UTC-4, John Mettraux wrote:
>
>
> a) extract the stuck expression
> b) extract its workitem with #applied_workitem
> c) call storage.put_msg('reply', 'workitem' => applied_workitem)
>
That's pretty much what I ended up doing, except I called the
reply_to_parent directly rather than put_msg. Get a ProcessStatus, find
the right expression, then exp.reply_to_parent(exp.h.applied_workitem). I
learned a bit more about ruote internals as a result.
The flow definitely updated at that point. Unfortunately the whole
tree was in a cancelling state, which I didn't notice, so the flow
restarted from the beginning. Exactly what we didn't want, we were hoping
to restart the automation so that we didn't have to manually manage the
remaining work. Manual recovery would have been easier, but when you're
trying to sell an automation product, you don't want to have to go back to
the customer and tell them the automation failed. But at least I know how
to cope with this situation in the future, and I can tell management that
the problem is solved (or will be) in the latest ruote.
Thanks again for all the help!
--
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"ruote" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
