# Error thrown resolve\_required\_actions when checking for username in Keycloak

**URL:** <https://forum.keycloak.org/t/error-thrown-resolve-required-actions-when-checking-for-username-in-keycloak/20223>\
**Category:** Getting advice\
**Created:** [February 13, 2023, 5:21pm UTC](https://forum.keycloak.org/t/error-thrown-resolve-required-actions-when-checking-for-username-in-keycloak/20223 "2023-02-13T17:21:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![smg](https://avatars.discourse-cdn.com/v4/letter/s/f0a364/32.png) [@smg](https://forum.keycloak.org/u/smg)\
**Post date:** [February 13, 2023, 5:21pm UTC](https://forum.keycloak.org/t/error-thrown-resolve-required-actions-when-checking-for-username-in-keycloak/20223/1 "2023-02-13T17:21:44Z")

</div>

When our API calls Keylcoak, we are getting error resolve\_required\_actions and not able to fetch user details. Any idea what is causing this ?

---

<div class="post-metadata">

**Author:** ![chrisritchie](https://avatars.discourse-cdn.com/v4/letter/c/8491ac/32.png) [@chrisritchie](https://forum.keycloak.org/u/chrisritchie)\
**Post date:** [February 3, 2024, 9:23am UTC](https://forum.keycloak.org/t/error-thrown-resolve-required-actions-when-checking-for-username-in-keycloak/20223/2 "2024-02-03T09:23:11Z")

</div>

At some point in the past, the user has been asked to perform a task, such as verify email, update password. See here:

[https://wjw465150.gitbooks.io/keycloak-documentation/content/server\_admin/topics/users/required-actions.html](https://wjw465150.gitbooks.io/keycloak-documentation/content/server_admin/topics/users/required-actions.html)

If there are any “Required User Actions” you should be able to remove them from the Users \> Details page.

In my case there were no “Required User Actions” so I had to scratch around the database. There is a table ‘user\_required\_action’. You will need to delete from this table where ‘user\_id’ = \<your\_users\_subject\>.

In my case, it appears that even though the required actions had expired, they were still preventing the user from logging in.
