Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
Forum Index » Engagement Designer » ED : Instance flow task coloring fails sometimes   XML
Author Message

Joined: 13/01/2017 08:33:22
Messages: 25

Dear ED team,

it seems that the instance flow task coloring fails some times.

I can see nodes/task which are not colored even if it is clear that the flow went through on those nodes/tasks.
It happens with more flows quite offen.

I also can see this kind of log blocks in the ED logs:
[..] Found matching table string: <table id="1471973629497" style="border-collapse: collapse; position: absolute; font-size: 12px; color: rgb(0, 0, 0); font-family: Verdana; font-weight: normal; border-style: none; left: 255px; top: 372px; width: 150px; height: 110px;"><tbody>....</tbody>
[..] Task State is: Completed - Color is green
[..] java.lang.RuntimeException: java.lang.NullPointerException
[..] Getting call for id: null
[..] callId is null
[..] user is: null
[..] Max Retry time to get db connection: 20
[..] Key in Cache
[..] Key in Cache
[..] Key in Cache
[..] Key in Cache
[..] Key in Cache
[..] Looking for taskId: id="1471966646728"

You can find plenty from this in the attached log file.

The main issue with this is that if the coloring is not consistent then it makes debug impossible.

Kind regards:
katalin Orban

p.s. </table> is always missing as a closing tag from the end of the first row ("Found matching table string...") of this log box :)
 Filename EngagementDesigner.log [Disk] Download
 Description ED logs with plenty of coloring failure
 Filesize 3914 Kbytes
 Downloaded:  153 time(s)

This message was edited 1 time. Last update was at 07/02/2017 10:39:18


Joined: 24/07/2014 16:30:45
Messages: 45

What build are you on? There has been a caching issue where the WFi is executed on one node but other nodes might show an old cached status. It has since been fixed in a patch.
Besides, to give you some peace of mind, its only a viewing the audit (instance) bug - the instance has executed correctly.
We can provide you with the patch id, once you tell us which release build you are on.

Joined: 11/01/2017 14:42:30
Messages: 8

Hi katalin,

It would be great if you could also attach the WAS log file TextLog_<Date>_<Time>.log that can be found at /var/log/Avaya/sm/.
You could also upgrade to the latest GA version of ED: 3.3.
Let us know.

Go to: