not quite … it is the backend, specifically your yaml configuration file that is dynamically fetched and evaluated, that determines whether or not a pipeline can be triggered. If you have a trigger section in your yaml that evaluates to false, and no pipeline executes, a null object is returned to the user interface, hence the stacktrace.
but yes, we should do a better job of handling the null and surfacing why no pipeline executes.