Hi all

I'm making some tests with ruote-kit and "remote/noh human" participants (as seen in other thread)

Testing with ruote-amqp and a SmtpParticipant some errors arised (not ruote related: bad smtp server addres, and things like that)

Workflow instances with errors get "freezed" and no more workitems get dispatched. I think that if I take route-kit /processes/:wfid, remove the "errors" attribute and post it back the workflow instance will resume, but it needs some human intervention. There are some errors that can be ignored because don't affect the core of the workflow (like sending an e-mail notification), but other errors are critical (don't dispatch a workitem to an amqp queue) and need human intervention.

How can I deal with this errors, so some can be silently ignored (perhaps with a warning) and some others need manual intervention?

Perhaps querying /processes after posting a workitem and checking the error or there is some other approach?

Thanks

--
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

Reply via email to