nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Execution of Asynchronous workflow

demouser

Execution of Asynchronous workflow with example: Workflow configured with serviceTask1, serviceTask2, serviceTask3, serviceTask4, serviceTask5

UseCase1:
If serviceTask3 have some exception then will have one entry in ACT_RU_JOB with EXCEPTION_MSG_ exception message and if we try to rexecute the workflow using managementService.executeJob(Id) it starts from serviceTask3.

UseCase2:
If serviceTask3 due to some exception wll have one entry in ACT_RU_JOB with EXCEPTION_MSG_ as empty and if we try to rexecute the workflow using managementService.executeJob(Id) its not starting form serviceTask3, Why again it starts form serviceTask1 ?

Is there any thing missing to throw the exception in a specified format.?

Find more posts tagged with

Comments

jbarrez

Depens on how you configured the process: are all the service tasks asynchrounous?
If so, then you will always roll back to the last stable state, ie the previous service task.

If only the first one is async, you will always roll back to the first one.

demouser

All the servicetask conifgured as asynchronous.

frederikherema1

If all service-tasks are configured as asynchronous, each of them will be executed in their own job, each persisting the state to the database when the complete successfully. So the DB will contain a pointer to service task 3 after the failed execution of job. So the next time it executes, it will execute service task 3 again. There is no specific format for the exception to have in order to be picked up as a failed job. When an exception has no message, the EXCEPTION_MSG_ will be empty, but the reference to the stacktrace will be filled in.

Double-check if ALL service-tasks are marked as asynchronous. If this is the case, and you still get this behaviour, try ripping out all unneeded code and create a failing unit-test, demonstrating this problem. Then we can look at this asap… See the sticky in the forum for guide on creating a unit-test project.