Database Reference
In-Depth Information
faulted instance in the console, we see how the instance retried itself and pro-
cessed successfully.
By clicking on
CreateCustomer2
to drill down in that component's flow, the out-
put is as shown in the following screenshot. Here, we can see that there was an
invocation to an external service, which apparently took 20 seconds (compare
4:05:02
to
4:05:22)
. It turns out that we have a 20 second timeout configured on
this reference. Excellent! This is the behavior we prefer. However, referring back
to the preceding screenshot, we see that the instance was retried. This turns out
to be a function of the fault policy attached to this particular composite. A job
well done by the developer! The composite has retried and the subsequent in-
vocation went through just fine. Note that the retried instances are actually new
instances.
The reason why we see both the original transaction and the retried one in the
same flow trace is because the same ECID is maintained when the instance re-
tries.
