---
title: "Missing Assertions in Autify: Troubleshooting Guide | Autify"
slug: "unable-to-select-desired-assertion"
description: "Learn How to Troubleshoot and Resolve Issues with Missing Assertions in Autify Automation Testing. Get Started Today!"
updated: 2022-09-07T10:01:41Z
published: 2022-09-07T10:01:41Z
canonical: "help.autify.com/unable-to-select-desired-assertion"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.autify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why doesn't the desired assertion appear when recording?

If you cannot record an assertion after clicking an element, or if the desired type of assertion does not appear as an option, the following may be the cause.

### You have selected a different element close to the one you intended.

First, please ensure you have selected the correct element on which you want to use the assertion. The type of assertion available depends on which element you select. For example, suppose you want to use an assertion that checks whether a button is enabled (clickable) or disabled (non-clickable). In this case, you need to select a `<button>` element. If you select a element that's close to the intended one (such as a parent or sibling element), you may not see the "Element Should Be Enabled / Disabled" assertion.

- [Assertions on elements in a page](https://help.autify.com/v1/docs/en/assertion-elements-on-the-page)

### The CSS property `pointer-events: none` is applied to the target element.

If you cannot record an assertion on the desired element, the element may have the CSS property `pointer-events: none` applied to it. If this CSS property is applied, event firing will be disabled, and the Autify Recorder cannot record actions on the element. In this case, there are two workarounds:

#### 1. Remove `pointer-events: none`

You can remove the style by changing your website, or temporarily disable the property via Chrome DevTools. We recommend this workaround as it will allow Autify Recorder to recognize the element, but if it doesn't work, please try the next solution.

#### 2. Use the assertion step you created when `pointer-events: none` was not applied

As an example, here is a workaround for validating whether a button is enabled or disabled. The following condictions must be met to use this workaround:

- When the button is enabled, you can focus on the target element and create an `Element Should Be Enabled` step.
- When the button is disabled, you cannot focus on it due to the `pointer-events: none` property and the "Element Should Be Disabled" assertion does not appear.

If these conditions are met, you can verify that the button is invalid in the following way:

1. Copy the "Element Should Be Enabled" step from the scenario (if the step does not exist yet, please create one by recording it).
2. Open the "Element Should Be Enabled" step that you copied, select "Element Should Be Disabled" in the Action section, and save it.  

![change-action-en.png](https://cdn.document360.io/a099d8a2-cfd2-42ca-9906-68b4a337f4a5/Images/Documentation/change-action-en.png?sv=2026-02-06&spr=https&st=2026-11-11T14%3A42%3A46Z&se=2026-11-11T15%3A42%3A46Z&sr=c&sp=r&sig=trIQoFz3XFyk%2BPeePDQNzfkUvf7C0p%2FN5aTsOd%2B9rh0%3D)