question

Laurenz Peleman avatar image
0 Likes"
Laurenz Peleman asked Patrick Zweekhorst answered

Trouble with acquire activity while debugging ProcessFlow

Hello everyone

I have been noticing an issue when trying to debug in ProcessFlow by stepping through the flowcharts: when having caught a token in an activity and stepping through an acquire activity that is not successful (Wait timer is fired), the debug step mode seems to stop, and the code executes until the next breakpoint, debug or error is encountered, or until all events at the particular moment have been executed. Is this common behaviour and if so, how can it be stopped so that I can keep stepping through my logic?

Kind regards

Laurenz Peleman

debug
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

·
Patrick Zweekhorst avatar image
0 Likes"
Patrick Zweekhorst answered

Hi @Laurenz Peleman ,

You could try to add a delay activity with a delay of 0 after the acquire activity. This will make sure that the token also stops after the wait timer is fired, since the delay activity will create a new event. This will sometimes also cause that you are able to step through the next activities in process flow.

· 1
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Laurenz Peleman avatar image Laurenz Peleman commented ·

Hi @Patrick Zweekhorst

Thanks for the suggestion of the 0 delay, they did the trick!

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.