Is it good practice to use non interrupting intermediate message catch event on boundary of receive task in camunda -
why did this:
the reason use kind of approach because want workflow wait @ node until video gets copied, @ same time want notified % of progress made while copying sent different application @ every 2s.
problem faced:
at random while executing workflow intermediate message catch event on boundary not registered , error first callback video copy application when tries correlate message event on boundary.
their others ways making simple loop in camunda achieve same behavior
but random error in case concern if 1 knows same issue or if better approach can me.
the approach non-interrupted boundary event valid, maybe bit verbose. prefer on loop construct, have thought "just" updating process variable outside indicate status? not need bpmn element allow this. see example rest api on update of process variables: https://docs.camunda.org/manual/7.7/reference/rest/process-instance/variables/put-variable/. same of course possible java api.
at random while executing workflow intermediate message catch event on boundary not registered , error first callback video copy application when tries correlate message event on boundary.
this should not happen , must have reason should try figure out. receiving message events work 100% in camunda itself, should search hint when occurs, or best extract small test case isolate problem.
Comments
Post a Comment