Preconditions (*)

1. Magento 2.3, 2.4

Steps to reproduce (*)

1. Login by user account
2. Create new order by checkout (order id 11)
3. Go to https://domain.com/sales/order/printInvoice/invoice_id/11/

Expected result (*)

1. If the invoice doesn't exist, Error handling should be done for better user experience.

Actual result (*)

1. Showing error:

There has been an error processing your request
Exception printing is disabled by default for security reasons.

Error log record number: 1a010b4dc79669c5758ea8eed7d18e4a4901fd402b6734616e693dfedb4c0cbd

Var/log/exception.log:
[2021-08-16 12:00:54] main.CRITICAL: The entity that was requested doesn't exist. Verify the entity and try again. {"report_id":"5aade6c95721635595e8acabec9909a13f5cf2ca4212e0313cd3e939ba435167","exception":"[object] (Magento\Framework\Exception\NoSuchEntityException(code: 0): The entity that was requested doesn't exist. Verify the entity and try again. at /var/www/html/magento2.4/magento2/app/code/Magento/Sales/Model/Order/InvoiceRepository.php:75)"} []

Note: There is no issue for the Orders having invoice generated from admin and navigated to /sales/order/printInvoice/invoice_id/7/

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.