To permanently remove a Business Transaction, the analyst must first exclude it from transaction detection and then delete it from the Business Transaction list. Deleting the transaction alone removes its current registration and associated visibility from the Controller, but the Application Agent can rediscover and register it again when matching traffic is observed.
An exclusion rule prevents future requests matching the specified entry point or transaction criteria from being detected as that Business Transaction. After the exclusion is configured and applied, the existing Business Transaction can be deleted safely without being recreated by automatic discovery.
Business Transaction Automatic Cleanup removes stale or inactive transactions according to retention and cleanup criteria; it does not prevent an active transaction from being rediscovered. Merely deleting the transaction from the list is therefore temporary when matching requests continue. Modifying a detection rule may alter transaction classification, but the explicit and reliable method for permanent removal is to exclude the transaction before deleting its existing registration.
Relevant CAAPA Study Guide topics include Business Transaction Detection, Exclude Rules, Automatic Discovery, Business Transaction Registration, Transaction Cleanup, and Business Transaction Management.