Stephen Russett
Stephen Russett
@fjtirado I see that as a destructive change, where a draft should be viewed as a non-destructive change: something that can be undone, abandoned, and not necessarily destroying the original...
Thanks @fjtirado this is a common issue/design consideration in other BPM engines: given this i would ask that deep level of design considerations be documented for the provided persistence add...
Added additional details above.
@wmedvede 1. If the execution of the job takes "hours" to complete, does the JS keep the HTTP connection active? Is the thread keep active on the JS side? Or...
>Finally we have a kind of 1.3) scenario, where the REST call could be done, the corresponding node was triggered but the process failed internally for some reason. In these...
>What we keep in this Job history table is the last status, but not all the status changes for a particular job. So we do not see that a Job...
@wmedvede thank you for the details. So what is the protocol for resolving these dead jobs / frozen process instances / activities? If the job is set to fail in...
@tiagodolphine the App **would** know about the error, as the error is occurring within the App's execution. But the App is unable to associate the error with the JS attempted...
>the process instance follows what is defined to handle errors in the process I think what we are getting refinement/clarity on is the Kogito JS and general async job execution...
related issue: https://issues.redhat.com/projects/KOGITO/issues/KOGITO-5863