---
sourceDocument: Brazil ServiceNow AI Platform user interface
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-user-interface
Release :
- brazil
ft:locale :
- en-US
ft:publication_title :
- Brazil ServiceNow AI Platform user interface
ft:clusterId :
- platux
bundleId :
- platux
workflow :
- Platform
---
# Navigation action cancellation
# Navigation action cancellation {#ariaid-title1}
Release version: Brazil
Updated September 10, 2026
 2 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of Navigation action cancellation
The Navigation Action Cancellation feature in ServiceNow's Request Manager enables users to cancel ongoing navigation actions by selecting a different application navigator link.
This functionality is critical for improving user experience by allowing cancellation of slow-loading transactions without waiting for completion.
Show full answer Show less
Cancellation behavior depends on system properties and transaction settings, ensuring controlled and predictable cancellation of navigation requests.
## Key Features
* **Cancelable transactions:** Both the original and new navigation actions must be marked cancelable (sysparmcancelable=true) or the original must be on the always cancelable allow list.
* **Always cancelable list:** Administrators can define modules (typically read-only such as dashboards, reports, or knowledge articles) that users can always cancel via the `glide.requestmanager.alwayscancel` system property.
* **Reference field query cancellation:** Allows cancellation of auto-completer queries in reference fields when users refine search input, controlled by `glide.requestmanager.cancelreferencecompleter`.
* **Configurable cancellation behavior:** The main toggle `glide.requestmanager.cancelothertransaction` enables or disables automatic cancellation of navigation actions.
## How Cancellation Works
The Request Manager evaluates the cancelability of both the current and new transactions when a user navigates. Cancellation occurs if conditions based on system properties and transaction flags are met, enhancing responsiveness and preventing unnecessary waits.
## Practical Use Cases
* A user navigates from one module (e.g., homepage) to another (e.g., incident list) and cancels the first navigation if it is slow.
* A user cancels navigation from read-only modules such as reports by navigating elsewhere, leveraging the always cancelable list.
* A user refines a reference field search query, cancelling the previous auto-completer request to improve efficiency.
## Administrative Controls
* Administrators can customize the always cancel list by adding UI pages or links, enabling cancellation for additional modules.
* Cancellation can be explicitly prevented for specific modules by modifying their module definitions, ensuring critical transactions remain uninterrupted.
The Request Manager allows users to cancel any navigation action they select from the
application navigator by clicking another application navigator link. System properties work
with settings for the table to allow navigation action cancellation.
This allows users to cancel slow loading transactions without having to wait for the previous
transaction to complete.
One of the following conditions must be true for the Request Manager to cancel a transaction.
* Both the original transaction and new transaction are cancelable (both transactions have the setting sysparm_cancelable=true).
* The original transaction is a member of the always cancelable allow list (the module is listed in the glide.request_manager.always_cancel system property) and the new transaction is cancelable (has the setting sysparm_cancelable=true).
* Both the original and new transaction produce an auto-completer query in a reference field.
{#c_CancelingNavigationActions__ul_ol4_hjq_n4}
## Cancellation workflow
The Request Manager uses the following workflow to determine whether to cancel a transaction. Figure 1. Cancel navigation actions {#c_CancelingNavigationActions__table_fn3_kkq_n4__entry__2}
| Property | Description |
|-|-|
| glide.request_manager.cancel_other_transaction | Enables or disables automatic cancellation behaviors. When true, users can cancel one navigation action with another navigation action. Type: true \| false Default value: true Location: sys_properties table |
| glide.request_manager.always_cancel | A comma-separated list of URIs that users can always cancel by clicking another navigation action. Typically items on this list are modules that provide read-only data such as dashboards, reports, or knowledge articles. Type: string Default value: home,sys_report_template Location: sys_properties table |
| glide.request_manager.cancel_reference_completer | Cancels a user query in a reference field when the user enters more information. For example, if the user starts an AJAX search in the Problem number field by entering PRB and then enters PRB000, the second query cancels the first query. Type: true \| false Default value: true Location: sys_properties table |
[Table 1. Navigation cancellation system properties]
{#c_CancelingNavigationActions__table_fn3_kkq_n4}
## Use cases {#c_CancelingNavigationActions__section_lpy_q4w_j1b}
There are three use cases where administrators can control user cancellation actions.
1. A user clicks a module, such as the homepage (home.do), and while waiting for the module to load decides to navigate to another module, such as the list of open incidents (incident_list.do). The system property glide.request_manager.cancel_other_transaction controls this use case.
2. A user clicks a module that displays read-only data, such as a report (sys_report_template.do?sysparm=sysid), and while waiting for the module to load decides to navigate to another module, such as the list of open incidents (incident_list.do). The system properties glide.request_manager.cancel_other_transaction and glide.request_manager.always_cancel control this use case.
3. A user starts typing a query in a reference field, such as entering PRB in the related Problem field and while waiting for the auto-completer to display results, decides to enter more information, such as PRB000. The system properties glide.request_manager.cancel_other_transaction and glide.request_manager.cancel_reference_completer control this use case.
{#c_CancelingNavigationActions__ol_tsp_qlq_n4}
* **[Add sites to the always cancel list](https://www.servicenow.com/docs/iI2_yxqy~iZi~d5WeNcPAw)**
You can add UI pages or other links to the always cancel list so that users can cancel actions on these pages by navigating to another module or link.
* **[Prevent users from canceling module transactions](https://www.servicenow.com/docs/InphTkcMzF3qreDztMPIww)**
You can explicitly prevent users from canceling the activity of a module by updating the module definition.