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; } } }

Provision of pause/resume and retry functionality as part of process engine

debadarsini

Hi,

We wanted this functionality for our project.

We had to create a custom signalable activity behaviour implementation to provide resume/pause and retry functionalities.

Can this be included as part of the activiti engine itself?

If required me and my team can contribute.

Let us know your thoughts.

Regards,
Debadarsini
maryrani ( Mary Rani)
ak1801(Akshit)

Find more posts tagged with

Accepted answers

cjose

A little late to the party here..how different in the pause/resume requirement to the already existing suspend/activate function in the activiti engine? Some references to suspend/activate feature is given below.

https://www.activiti.org/userguide/#api.services.suspend
https://www.activiti.org/userguide/#_suspend_a_process_definition
https://www.activiti.org/userguide/#_activate_or_suspend_a_process_instance

All comments

anilmann

Hi Debadarshini,

I am too trying to implement same stuff. It will be of great help if you can share the code.

Thanks in Advance.

spalloin

Hi all,

we also want to add this functionality to our project. Our use case is to retry a failed service task without restarting the whole workflow. Moreover this functionality shall be accessible via a REST call.

I've made some research and found that this feature has already been asked quite a few time.

How to implement restart/pause/resume in Activiti

activiti-unit-test-grasshopper/MyUnitTest.java at master · martin-grofcik/activiti-unit-test-grasshopper · GitHub

The last link gives some unit test and code for a 'RestartInstanceActivitiCommand'. However I'm not able to integrate it to our use case.

The current solution I'm investigating is by using an error boundary event to catch the service task failure. This error boundary event is linked to a receive task waiting for a signal to restart the service task, as the following figure illustrate :

This diagram work well, as we are able to successfully retry the service task when it fail, but the workflow does not seems to reach the end event when the service task is finally successful. The process instance isn't ended.

Any hint or advice for another strategy in order to implement this feature will be greatly appreciated.

Best Regards.

thuynh

Hi Sylvain,

I've tried your pattern in my sandbox and was successfully able to reach the end of the instance.

-------------------------------------------------------

T E S T S

-------------------------------------------------------

Running org.activiti.designer.test.PaymentProcessTest

Dec 16, 2016 2:05:40 PM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions

INFO: Loading XML bean definitions from class path resource [activiti.cfg.xml]

Dec 16, 2016 2:05:43 PM org.activiti.engine.impl.db.DbSqlSession executeSchemaResource

INFO: performing create on engine with resource org/activiti/db/create/activiti.h2.create.engine.sql

Dec 16, 2016 2:05:43 PM org.activiti.engine.impl.db.DbSqlSession executeSchemaResource

INFO: performing create on history with resource org/activiti/db/create/activiti.h2.create.history.sql

Dec 16, 2016 2:05:43 PM org.activiti.engine.impl.db.DbSqlSession executeSchemaResource

INFO: performing create on identity with resource org/activiti/db/create/activiti.h2.create.identity.sql

Dec 16, 2016 2:05:43 PM org.activiti.engine.impl.ProcessEngineImpl <init>

INFO: ProcessEngine default created

Dec 16, 2016 2:05:43 PM org.activiti.engine.impl.bpmn.deployer.BpmnDeployer deploy

INFO: Processing resource paymentProcess.bpmn20.xml