the infamous 'failed to signal transition'

[lucille_arkenst]

Hi all,

Can somebody please tell me – How can I look into the "guts" of the workflow, so I can see what's going on?  And fix the problem(s)?  The reason I got the "failed to signal transition" error on my custom workflow was because the AlfrescoScript inside the workflow, whose purpose is to email the users, supposedly is trying to access a "properties" object that doesn't exist.  (This properties object is the workflow array's child object.  Which should exist!)  I know this by looking at alfresco.log.

This workflow only fails periodically, and I have no idea why.  But I've used the console to try to push the workflow to the next task, to no avail.  Same error. 

And I've read Jeff Potts' article on enabling the AlfrescoScript error log, but when I restarted Alfresco, it complained that it was missing some sort of X11 component.  (According to the log output).

Also, I'm using Alfresco 3.3… I would LOVE to upgrade, but I have a bunch of customizations, and I'm so afraid they might break if I upgrade.

Please help…

Thanks in advance,
Lucille

[afaust]

Hello,

the X11 error is probably due to an attempt at enabling the debugger (not to be confused with the script logger) which requires some kind of graphics environment to run. If you run Alfresco in a headless environment, this is the expected result and the debugger can't be used.

Apart from remote debugging the Java parts that call your workflow script I don't see a practical way of getting to the root of the error (the reason why that "properties" object doesn't exist).

Regards
Axel