Warning in log file "Could not chain"

RE: Warning in log file "Could not chain"

jeanalainb0001 — Mon, 13 Mar 2023 06:52:29 GMT

Hi Abhay,

I don't agree with you. You forgot that the process is called by a Web API. Chaining is required to have the result of the enitre process instance.

For example :

If I have a process chained that call synchronously a subprocess not chained

I receive { "abc" : "", "one" : 1, "two" : 0, "xyz" : "" } script activities after he first not chained root are not executed before the response is sent to the Web API

If the sub process is chained, I recieve { "abc" : "abc", "one" : 1, "two" : 2, "xyz" : "xyz" } that is the goal.

RE: Warning in log file "Could not chain"

jeanalainb0001 — Mon, 13 Mar 2023 06:28:52 GMT

Hi Mike,

It is a healthcheck on the database connexion. An external tool call this health check that do some test including this one and return result. The result must be formatted as the client want. If we have an error on the node that call the DB, the process stop with error. The goal of the timer is continue the process after a short periode of time. By this way we can construct the result and put inside that the business database is not responding in expected time.

RE: Warning in log file "Could not chain"

Mike Schmitt — Fri, 10 Mar 2023 20:39:03 GMT

Activity chaining is automatically broken as soon as the process flow reaches any timer node, so I'm not clear what you'd be trying to accomplish with this.

RE: Warning in log file "Could not chain"

Abhay Dalsaniya — Fri, 10 Mar 2023 20:35:34 GMT

Do you mean, you are using the process variables in the parent rule using fv!processInfo ? If not, then you don't need chaining because the sub-process runs synchronously.

RE: Warning in log file "Could not chain"

jeanalainb0001 — Fri, 10 Mar 2023 05:59:26 GMT

The process is under a Web API, the chaining is required to return the value calculated by expressions in the script activities even if the timeout is triggered

RE: Warning in log file "Could not chain"

davel001150 — Thu, 09 Mar 2023 16:20:10 GMT

Is it the chain from the timer to the timeout node? Why would a chain ever successfully originate from a timer event? It's not a user hoping to not get dropped.

RE: Warning in log file "Could not chain"

geethas018826 — Thu, 09 Mar 2023 07:56:54 GMT

Thanks for the reply jean

RE: Warning in log file "Could not chain"

jeanalainb0001 — Thu, 09 Mar 2023 07:55:38 GMT

Hi Geetha,

No. The chaining can be break if you have too many activities (>50 I think) or if the time i too long (>10sec) but in my scenario here the process work fine and return the result we want. It is just a warning into the log. We do not continue to investigate.

RE: Warning in log file "Could not chain"

Stefan Helzle — Thu, 09 Mar 2023 07:34:53 GMT

I think this is expected. The original idea of chaining was to forward the user in the UI to the user input task. Now, in such a scenario, the chain ends without any.

RE: Warning in log file "Could not chain"

geethas018826 — Thu, 09 Mar 2023 07:09:07 GMT

jeanalainb0001
Hi Jean
you got solution for this issue, we are facing similar issue