Why does the report display more check profiles than the editor?

When the editor is initialised the app passes so called thirdPartyAttributes to the Congree server. These attributes allow you to define fine granular rules for your check profiles. These attributes can further be extended as described in Custom Context.

Usually this mechanism is used to apply a filter to the available check profiles on the Congree server, so only a defined subset is available in the editor. Unfortunately the Congree REST API does not allow to set these attributes when querying the available check profiles directly. Thus no filter is applied and all check profiles are returned.