> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/access-control/troubleshooting/troubleshoot-a-stuck-latch-on-verkada-door-locks.md).

# Troubleshoot a Stuck Latch on Verkada Door Locks

Learn how to identify and safely troubleshoot a stuck latch on Verkada door hardware

In rare cases, the latch on older Verkada AL54 cylindrical locks can catch and become stuck. This is a known edge case that occurs only when a specific set of physical conditions is present simultaneously.

{% hint style="warning" %}
This issue only affects Verkada AL54 cylindrical locks shipped before July 2026. Units shipped in July 2026 or later use an updated lock body and are not affected.
{% endhint %}

***

## Release a stuck latch

{% hint style="danger" %}
Do *not* use excessive force to turn the handle or force the door open. Applying pressure to the handle while the latch is stuck can bend or break an internal component. If that component is damaged, the latch can no longer fully retract. This permanently affects lock function and can compromise door security.
{% endhint %}

{% stepper %}
{% step %}
**Release both handles completely.** 

Do not apply extra pressure to the handle or force the door open.
{% endstep %}

{% step %}
**Allow the latch mechanism to return to its resting state.** 

Instead of forcing the handle, release both handles simultaneously to allow the internal mechanism to reset to its normal resting state before attempting to use the door again.
{% endstep %}
{% endstepper %}

***

### Contact Verkada Support

If you cannot get the lock out of this stuck state, or if this issue happens repeatedly, [contact Verkada Support](/command/need-help/contact-verkada-support.md).

Verkada has an updated lock body that eliminates this edge case. Verkada Support can help you troubleshoot the issue and, if needed, start a replacement for updated hardware.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/access-control/troubleshooting/troubleshoot-a-stuck-latch-on-verkada-door-locks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.