Strange problem with BPM

[Former Member]

I have BPM

Blok1

Send Async step: Acknowledgement: Transport

Exception brach: CannotInsert

Deadline brach: Throw Exception CannotInsert

Block2

Mapping

Send

<b>BPM Monitoring</b>

Mapping

Workflow System Background work item created 13:33

Workflow System Background Processing Started 13:33 tRFC Entries

Workflow System Work Item Processing Complete <b>14:02</b>

Workflow System Result Processing 14:02

When I click on mapping I see

Current Creation 13:33 Start 14:02 End 14:02

When deadline throws an exception mapping works ~ 30 min

I have the same problem in other BPM with deadline.

Could someone explain me what is wrong with my BPM?

Message was edited by: Sergey A

[Former Member · Accepted solution]

Sergey,

You can set different options for the deadline branch. You should choose 'Creating the step'. This will cause deadline branch being triggered after 30 minutes of creating the first block.

You can also select e.g. 'Creating the process', this will cause the deadline to be triggered 30 minutes after creating the process, whereever the process is at that moment.

Kind regards,

Christiaan Schaake.

[Former Member · Accepted solution]

I choosed 'Creating the step' already. Timeout is 5 minutes. The problem is that steps after first block are working during different time. When I started BPM first time ~ 30 min . second time ~ 1 sec. BPM works unstable in case of Deadline branch.

[Former Member · Accepted solution]

Hi Sergey,

Did you check this thread ?

Regards

Anand

[Former Member · Accepted solution]

Yes.

I have read a blog with transport acknowledgement too.