0 votes
10 views
in Integrations by (10.6k points)

1 Answer

0 votes
by (10.6k points)
This is a known limitation/feature/issue of timer based UCAS, if the invoked service does not complete within a stipulated amount of time the UCA may fire twice/thrice.

There can be two solutions to this issue

1. Convert your service invocations to bpd instance based invocations, the UCA simply launches a BPD instance which in turn does the service call so that timeout does not happen in the UCA service.

2. another solution will be to create an EPV and record the date part of current datetime to it after every invocation and at the beginning of the invocation check if it is the same date do not invoke the activity.

Related questions

0 votes
0 answers 26 views
0 votes
1 answer 16 views
0 votes
2 answers 181 views
0 votes
0 answers 45 views
0 votes
1 answer 225 views
0 votes
0 answers 3 views
0 votes
0 answers 41 views
0 votes
3 answers 84 views
0 votes
1 answer 93 views
+1 vote
0 answers 41 views

494 questions

404 answers

81 comments

1.6k users

Created By Dosvak LLC (WWW.DOSVAK.COM)
Our Public Git Repository

Dosvak UI Toolkit --- Download --- Demo

Subscribe us at

Welcome to BPM Tips Q&A, Community wiki/forum where you can ask questions and receive answers from other IBM BPM experts and members of the community. Users with 2000 points will automatically be promoted to expert level.
...