Hello,
I see in a log file named "db_PX..." a lot of error : [Activity Chaining] Could not chain to attended activity. No attended activity with compatible assignment was found."
but the related process seem working fine and I do not see any specific. The process is called by a webAPI and the result of the process is returned as result by the WebAPI.
The process is very simple.
The sub process called is
Have you already received a similar warning ?
I suspect the complex gateway.
Regards
Jean-Alain
Discussion posts and replies are publicly visible
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.
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
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.
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.
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.
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.