0 votes
30 views
in Integrations by (13.5k points)

1 Answer

0 votes
by (13.5k 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 29 views
0 votes
1 answer 44 views
0 votes
2 answers 202 views
0 votes
0 answers 49 views
0 votes
1 answer 241 views
0 votes
0 answers 5 views
0 votes
1 answer 31 views
0 votes
0 answers 47 views
0 votes
3 answers 93 views
...