# Block user issue

**URL:** <https://community.auth0.com/t/block-user-issue/89260>\
**Category:** Get Help\
**Created:** [August 23, 2022, 12:00pm UTC](https://community.auth0.com/t/block-user-issue/89260 "2022-08-23T12:00:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![flavio.cuellar](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/flavio.cuellar/32/39487_2.png) [@flavio.cuellar](https://community.auth0.com/u/flavio.cuellar)\
**Post date:** [August 23, 2022, 12:00pm UTC](https://community.auth0.com/t/block-user-issue/89260/1 "2022-08-23T12:00:11Z")

</div>

Hello.  
I’m trying to develop a logging system using the API.  
First of all, we have configured the “Brute-force Protection \> Maximum Attempts” to 5.  
We would like to show the attempts remaining when the user introduces a wrong password. To calculate this, we use the endpoint ‘/api/v2/users/{id}/logs’ to count the loggin fails.  
To know if the user is blocked, we use the endpoint ‘/api/v2/user-blocks/{id}’ with the parameter: consider\_brute\_force\_enablement=true.  
The point is that an user fails 5 times, the user doesn’t receive the email. Then, the next time, even if the user introduces the correct password, the user will receive the email with the blocked information.  
Many thanks for any help in advance

---

<div class="post-metadata">

**Author:** ![lihua.zhang](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/lihua.zhang/32/39683_2.png) [@lihua.zhang](https://community.auth0.com/u/lihua.zhang)\
**Post date:** [August 27, 2022, 12:37am UTC](https://community.auth0.com/t/block-user-issue/89260/4 "2022-08-27T00:37:55Z")

</div>

Hi @flavio.cuellar ,

Sorry for the delay in the response and welcome to the Auth0 Community!

What you observed is the expected behavior. After 5 consecutive failed login attempts, further attempts will block the account, that’s why you received the email notification on the 6th attempt.

Hope this helps!

---

<div class="post-metadata">

**Author:** ![flavio.cuellar](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/flavio.cuellar/32/39487_2.png) [@flavio.cuellar](https://community.auth0.com/u/flavio.cuellar)\
**Post date:** [August 29, 2022, 5:39am UTC](https://community.auth0.com/t/block-user-issue/89260/5 "2022-08-29T05:39:51Z")

</div>

Hi @lihua.zhang

I was expecting the email at the moment when the account is blocked, at the 5th attempt.

Thanks for your answer.

---

<div class="post-metadata">

**Author:** ![lihua.zhang](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/lihua.zhang/32/39683_2.png) [@lihua.zhang](https://community.auth0.com/u/lihua.zhang)\
**Post date:** [August 29, 2022, 2:15pm UTC](https://community.auth0.com/t/block-user-issue/89260/6 "2022-08-29T14:15:56Z")

</div>

Hi @flavio.cuellar ,

I understand your concern. Please feel free to communicate your use case with our Product team directly via the [feedback](https://auth0.com/feedback) page. Thanks!

---

<div class="post-metadata">

**Author:** ![lihua.zhang](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/lihua.zhang/32/39683_2.png) [@lihua.zhang](https://community.auth0.com/u/lihua.zhang)\
**Post date:** [September 14, 2022, 5:40am UTC](https://community.auth0.com/t/block-user-issue/89260/7 "2022-09-14T05:40:58Z")

</div>


