# Updated state pamd module

**URL:** <https://forum.ansible.com/t/updated-state-pamd-module/42925>\
**Category:** Get Help\
**Tags:** ansible, ansible-core\
**Created:** [May 22, 2025, 2:29pm UTC](https://forum.ansible.com/t/updated-state-pamd-module/42925 "2025-05-22T14:29:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![marseaplage](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marseaplage/32/2552_2.png) [@marseaplage](https://forum.ansible.com/u/marseaplage)\
**Post date:** [May 22, 2025, 2:29pm UTC](https://forum.ansible.com/t/updated-state-pamd-module/42925/1 "2025-05-22T14:29:13Z")

</div>

I have similar problem to the reported on this link [https://forum.ansible.com/t/help-with-pamd-module/28698](https://forum.ansible.com/t/help-with-pamd-module/28698) .  
The updated state of [the pamd ansible module](https://docs.ansible.com/ansible/latest/collections/community/general/pamd_module.html) is not replacing the policy when it matches type, control and module\_path but instead create one new.  
Could you please give me any suggestion to solve the inconvenient?