John Mettraux wrote: > > Hi Boris, > > the analysis seems fine. > > 1). is only this 'translate' subprocess concerned ? Are other missing > subprocesses causing this "preapply failed" ?
no, it looks as if many or all subprocess definitions are affected > > 2). is the "translate" string used as a variable name in some other > flow ? (i.e. could the translate variable get unbound at engine level > due to something like <unset variable="//translate" />, just an > hypothesis). Yes I figured that this might be a possible cause, but see 1.) ...somewhat unlikely. > 3). could I have a look at the "engine environment" as stored on the > disk ? (It should be somewhere at the root of the expression pool with > a well recognizable name). The expression as stored for your > production env would be perfect. Seems I cannot post attachments to this list...I have sent you the file directly. By the way, once the vars are "unset", everything sooner or later fails (proceed, launch), and results in lost workflows. (how about a setting that does not drop the workitems but stores them in a "failed" store?) I have additionally in the logs lots of "failed to load expression" entries, even after launching a new workflow. Maybe that is related. Thanks Boris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFE users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwfe-users?hl=en -~----------~----~----~----~------~----~------~--~---
