is there any way to hide/suspend instance for some period of time (lets say 5 minutes) and after, it become available again. https://i.imgur.com/Nh3TGmY.png
i need this instance to be untouchable at current step for some period of time and then become available and i can handle it and move to the next step.
im processing data in Node.js, so rest api way or through the diagram way may be exists some block where instance can chill for some time and then camunda push it to the next step and if it fails there return it back to the “chill” block with some counter to delete after to avoid endless attempts …
im very new in camunda and need your advice how to do it right. At the moment i see a way to add few variables inside (timestamp and counter) and suspend-continue or delete-move in another block-restore but both of them doesnt look good to me
I’m not sure what you want to process in Node.js, but at least you can pause a process-instance by an Timer Intermediate Catching Event: Timer Events | docs.camunda.org
Hi, thank you, this is part of what im looking for.
how to organize counter to prevent endless loop like:
token enter some step
processed
enter into the timer and wait for the 5 mins
timer release token and token enter the next step
if step(task) receive “complete” signal then token continue his journey
if task receive “fail” signal (im not sure how to send it yet) then token returns back to the timer
some where in between lopp back to the timer or after the timer should be placed some counter.
as i see it could be realized like IF condition block which will check some variable inside token and if it is equal to let say 3 times will move token to some “collector” of this kind of tokens (and later they will be deleted or so). but rises another question how to increment this counter value within camunda …
If you mean with failure something like an exception, then you should not integrate the retry-behaviour as part of process-model using timer-events (> *). In this case you can specify the number of retries by configuring the Retry Time Cycle like e.g. R3/PT5M which means 3 retries with a timeout of 5 minutes each. Doing so you don’t have to take care of a counter at all.
