A lost and found transaction is an executed SubPath of a Transaction that have not been linked to it's parent SubPath.
The two primary reasons for a transaction to fall into Lost and found category 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 the agent.
This typically happens on long running transactions that run into the server timeout of 1 hour or the transaction-size limit and these transactions keep starting SubPath's on the agent.
Lost & Found transactions are shown in the PurePath dashlet. No special configuration is needed to display them.