Hi @senthilengg. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.

  3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.

  4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  5. Add label Issue: Confirmed once verification is complete.

  6. Make sure that automatic system confirms that report has been added to the backlog.
  To pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.

Hello @senthilengg,

Thanks for the report and collaboration!

We have tried to follow the mentioned steps and for us, the indexer_state has been updated:

Previously it was something like below:

After running bin/magento s:up && bin/magento cache:clean:

The hash_config is also updating. But it seems to us an intended behaviour please let us know the expected and actual result to understand more about the issue.

Thanks

@engcom-Hotel Its not only updating the hash of the indexer but also regenerate the whole grid data again. Assume a situation if you have 4 million customer data and the grid table got truncated and recreated then it introduces significant downtime for no use.

Ideally the encryption key should update the hash alone and not the grid data because there is no business need to do that and it creates a huge downtime for the merchants if they have million plus customers.

Expected Result : Hash should update on the indexer_state without regenerating the grid data.
Actual Result: Grid table getting truncated and getting recreated again for no reason.