Hi, We have complete tempo based application and chaining breaks here

anagha_abhyankar over 10 years ago

Hi,

We have complete tempo based application and chaining breaks here sometimes.
I know if the time consumed by nodes is more than 8 secs, then it is desirable or it will break even if no of nodes exceeds between two screens.

Is there a way that I can count exact time consumed by each and every node? I tried to check Process Nodes in Process Details, am I on the right track?

Regards,

Anagha...

Discussion posts and replies are publicly visible

Parents

0 Eduardo Fuentes
Appian Employee
over 10 years ago

That's correct, that's a good place to monitor. Also review the db_PX*.log that correspond to the engine where your process where the chaining broke.

db_PX001*.log: EXEC00
db_PX011*.log: EXEC01
db_PX021*.log: EXEC02

You can determine in what engine a process is running by adding a column to the Processes report defined as

=process_ee_id()

a) This is what you will see if the number of nodes is exceeded (in the example my model is called "My model")

2014-06-24 05:38:32 [PX001] {pe40.kdb 759} (Default) WARN .a.p.PROCESS.i "[P25-My model with activity chaining] [Activity Chaining] Could not chain to attended activity. Limit of 50 unattended nodes executed was reached."

b) This is what you will see if the activity chaining breaks for other reason (such as time, a timer or non-chained paths)

2014-06-24 06:21:58 [PX021] {pe41.kdb 644} (Default) WARN .a.p.PROCESS.i "[Activity Chaining] Could not chain to attended activity. No attended activity with compatible assignment was found."
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eduardo Fuentes
Appian Employee
over 10 years ago

That's correct, that's a good place to monitor. Also review the db_PX*.log that correspond to the engine where your process where the chaining broke.

db_PX001*.log: EXEC00
db_PX011*.log: EXEC01
db_PX021*.log: EXEC02

You can determine in what engine a process is running by adding a column to the Processes report defined as

=process_ee_id()

a) This is what you will see if the number of nodes is exceeded (in the example my model is called "My model")

2014-06-24 05:38:32 [PX001] {pe40.kdb 759} (Default) WARN .a.p.PROCESS.i "[P25-My model with activity chaining] [Activity Chaining] Could not chain to attended activity. Limit of 50 unattended nodes executed was reached."

b) This is what you will see if the activity chaining breaks for other reason (such as time, a timer or non-chained paths)

2014-06-24 06:21:58 [PX021] {pe41.kdb 644} (Default) WARN .a.p.PROCESS.i "[Activity Chaining] Could not chain to attended activity. No attended activity with compatible assignment was found."
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data