Authoring login outage caused by pending requests panel on home page

Issue: There is a login issue was caused by the exception not being caught and handled anywhere.

Steps/ Details of issue: An outage occurred in production where authors were unable to login to the CMS. All users observed a 408 timeout error page.

When investigating this further, some errors in the logs were found.
-----------------
13.02.2024 23:54:37 ERROR https-openssl-apr-8443-exec-144 [JcrItemModel.doSave:318] javax.jcr.ItemNotFoundException: failed to build path of 3070c581-55e3-41ba-9966-89c35593d829: 0b6eb4b5-0130-48a0-a56d-88adfeb67804 has no child entry for 3070c581-55e3-41ba-9966-89c35593d829
13.02.2024 23:54:37 ERROR https-openssl-apr-8443-exec-144 [TodoPlugin$TodoView.populateItem:83] Failed to create todo item from publication request node
javax.jcr.ItemNotFoundException: failed to build path of 3070c581-55e3-41ba-9966-89c35593d829: 0b6eb4b5-0130-48a0-a56d-88adfeb67804 has no child entry for 3070c581-55e3-41ba-9966-89c35593d829
-----------------

When looked for these UUIDs in the repository, it looked like the node was deleted, but the query that was used still attempted to select this node, and ran into the exception.

An exception was coming from the Home Page's 'Pending Requests' panel, where it tries to find all hippo:request node types to display these. The issue was caused by a corrupt repo it seems, where a full index rebuild resolved it.

The login issue was caused by the exception not being caught and handled anywhere.

Request: Would it be possible to wrap this query with a try catch in the implementation such that on failure to display something in this panel, it doesn't prevent all users from logging in to the CMS?

Need an error message on that panel if such issue occurs and that allows to investigate, instead of a system outage.