On Thu, Jan 24, 2013 at 09:14:39AM -0800, EJI wrote: > > If I'm interpreting it right, the workflow fails after approval_process is > reached. However, the workflow also doesn't list any errors.
Hello Eji, OK, I think you solved that one by removing the on_error in your next email. > I know the information doesn't really jive together that well, and it may > be that there are multiple causes in the mix. I have a few questions which > will hopefully narrow this down: > > - Are there any inherent issues with implementing Ruote on Heroku? Are > there any "gotchas" that we need to consider? You have to know a bit more about ruote and Heroku. > - If there are exceptions to be caught, which is the best way to catch > them? I've tried using on_error in my process definition, but I can't tell > if it's actually being tripped (I can't log or trace anything from within > the block) You have to make sure your errors are not silenced. Beyond that, whether it sends you a sms or electrocutates your project manager, it's company policy, as long as it's not silent. > - Is there any way to observe the worker process to see if it is > experiencing issues? You could place a process observer http://ruote.rubyforge.org/process_observation.html https://github.com/jmettraux/ruote/blob/a5411e75dba1ce3d5ed0544119e819068724b953/lib/ruote/observer.rb and make it emit info similar to the NOISY mode to some log. > - Could moving the launcher within a rake task alleviate this sort of > behavior? I don't think changing the colour of the wrapping paper will change the taste of the chocolate, unless... Best regards, -- John Mettraux - http://lambda.io/jmettraux -- -- 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
