0 votes
17 views
in Integrations by (11.7k points)

1 Answer

0 votes
by (11.7k 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 27 views
0 votes
1 answer 26 views
0 votes
2 answers 185 views
0 votes
0 answers 46 views
0 votes
1 answer 229 views
0 votes
0 answers 3 views
0 votes
3 answers 87 views
0 votes
0 answers 42 views
0 votes
1 answer 113 views

515 questions

423 answers

81 comments

1.6k users

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.
...