Errors when an alert checker matches an interface for which the polling is disabled

When an alert checker attempt to check criteria on an interface which is disabled (and, therefore, for which no RRD file exists) then two issues occur:

1 - The web interface errors and is unable to render the full page.
2 - The main home page lists these alert matches as 'unknown' but you cannot view them either.

I've been poking this and so far have tied it down to interfaces which are disabled, but then the alert checker matches them to try to check for breaches (like, for example, discarded packets greater than a given value).

A workaround is to re-enable the interface for polling. However, we have a large number of these disabled (with good reason) and it's not possible to find them all because the page that would list them will not render after it encounters the 'first' instance of an non-existent RRD. Meaning we can only find them one at a time

I will attach some visuals, as this isn't the easiest thing to describe...

I've reduced this to under 30 (was over 50) by random luck of finding alert checkers which might be triggering it (i.e. those that check ports) and then writing exclusions to skip what i think might be causing it.

It would be great if the error is sorted, and it handled the non-existent RRDs without issue, as the need to exclude certain interfaces from polling is quite useful. As is the ability to simply select 'all' interfaces in a checker and then filter them by their type, without fear of matching a non-polling port on a device somewhere.

Cheers!