Cryptic error message for INSAD input failure

[GiudGiud]

Reason

It complains about missing a UO when really it s missing the material

Design

Rework the call order to make the material be missed first

Impact

Need for user support on something simple

Thanks a lot, Guillaume. Following your advice I've been using a test input file with INSAD and from there created a new input file for my application, using INSAD instead of INS.

I now run into the following error which I struggle debugging:

*** ERROR ***
The following error occurred in the object "MOOSE Problem", of type "FEProblem".

Unable to find user object with name 'ins_ad_object_tracker'

which might be somehow linked to https://github.com/idaholab/moose/issues/15713?

Originally posted by @AdrienWehrle in https://github.com/idaholab/moose/discussions/26651#discussioncomment-8463771

[lindsayad]

I don't know what you mean by call order. But in INSAD residual objects we can probably query for the existence of an INSADMaterial before retrieving the user object and so give the meaningful error message you're asking for

[GiudGiud]

If we queried the material property earlier maybe we would get a better error. Your way sounds good