AppMon 2018 April feature A lost and found transaction is an executed SubPath of a Transaction, which is not linked to its parent SubPath.
The two primary reasons for a missing connection with the parent SubPath are:
- The child SubPath hasn't started within 10 seconds after the parent node has been received by the server.
- The parent SubPath has been completed by the server before the child SubPath has been started on an Agent.
This typically happens on long running transactions that run into the server's timeout of 1 hour; or when the transaction-size limit is exceeded but transactions are keep starting SubPaths on an Agent.
Lost & Found transactions are shown in the PurePath dashlet. No special configuration is needed to display them.