top of page

Active Transactions

Introduction | Search for Active Transactions | Kill Active Transactions | NOTE


 

Introduction

 

Anything that runs on ServiceNow uses a background thread that can be tracked under the Active Transactions module.


 

Search for Active Transactions (for Discovery Admin)

 

To search for Active Transactions:


  1. Navigate to: System Diagnostics > Active Transactions (All Nodes)

  2. Filter on: URL STARTS_WITH x_qune_da


If no records are returned with this Filter, there are no active Discovery Admin transactions running in the background.


If there are one or more results returned with this Filter, corresponding to the Background Queues used by Discovery Admin, the count signifies the number of threads currently allocated to Discovery Admin.


 

Kill Active Transactions (for Discovery Admin)

 

Follow the steps below to kill transactions via the Active Transactions module if:

  • you suspect a hung transaction or

  • you want to be sure, there are no active Discovery Admin transactions running in the background


  1. Search for Active Transactions

  2. Select (via Check Box - left of the row): One or more records in the List

  3. Click (Choice Box - bottom of the screen): Actions on selected rows...

  4. Select: Kill

    1. It may take a few seconds for ServiceNow to Kill the transaction(s)

    2. Search for Active Transactions to reconfirm successful deletion



 

NOTE

 

  • If you cancel an active Discovery Admin transactions using the steps above, there is no change in the status on the corresponding Troubleshooting record as the cancelation has been done via the backend, instead of the UI.

  • As a result, the Troubleshooting Record may look like it is hung in the Troubleshooting State or the Incident Generation State. Use the { Cancel } UI Action to change the State of the Troubleshooting Record.

  • If there are additional queued Discovery Admin transactions, these new transactions will start processing once the previous ones are killed. Thus you may need to search for and kill the Active Transactions several times to be sure, that there are no active Discovery Admin transactions running in the background.


bottom of page