[Issue] Customer account confirm - StateException should not be logged as critical error

[m2-assistant]

This issue is automatically created based on existing pull request: #39466: Customer account confirm - StateException should not be logged as critical error

---

Description (*)

The error "The account is already active," etc., should not be logged as a critical exception since it is more of a user error rather than a programming issue that needs to be addressed.
Instead of using "addException" which logs the StateExpection I changed to to a normal error message.

Manual testing scenarios (*)

• Create a customer account
• Confirm
• Confrm again

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @engcom-Bravo. 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.

[engcom-Bravo]

Hi @mvenghaus,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop magento instance and we are not able to reproduce the issue.Kindly refer the attached video.

Screen.Recording.2024-12-19.at.10.45.26.am.mov

We are not getting any error.Could you please let us know if we are missing anything and also please provide us screenshots or screencast.

Thanks.

[mvenghaus]

Hey,

thanks for taking care.

This is not visible to the user. It's messing up the exception log for developers. An exception should only be logged if it's critical and not based on the user's behavior.

Regards
Marcus