<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: the infamous 'failed to signal transition' in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/the-infamous-failed-to-signal-transition/m-p/283833#M236963</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 07 Sep 2013 15:42:31 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2013-09-07T15:42:31Z</dc:date>
    <item>
      <title>the infamous 'failed to signal transition'</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/the-infamous-failed-to-signal-transition/m-p/283832#M236962</link>
      <description>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?&amp;nbsp; And fix the problem(s)?&amp;nbsp; 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 th</description>
      <pubDate>Mon, 02 Sep 2013 11:01:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/the-infamous-failed-to-signal-transition/m-p/283832#M236962</guid>
      <dc:creator>lucille_arkenst</dc:creator>
      <dc:date>2013-09-02T11:01:12Z</dc:date>
    </item>
    <item>
      <title>Re: the infamous 'failed to signal transition'</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/the-infamous-failed-to-signal-transition/m-p/283833#M236963</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Sep 2013 15:42:31 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/the-infamous-failed-to-signal-transition/m-p/283833#M236963</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2013-09-07T15:42:31Z</dc:date>
    </item>
  </channel>
</rss>

