Skip to main content
Solved

Process Explorer stuck on infinite load with one specific Knowledge Model

  • September 24, 2026
  • 1 reply
  • 14 views
michael.hamme13
Level 5
Forum|alt.badge.img+6

The Process Explorer component keeps loading indefinitely when connected to one particular Knowledge Model. Everything else seems fine — Variant Explorer and Case Explorer work without issues on the same KM, and if I switch the Process Explorer to a different Knowledge Model in the same view it loads perfectly.

Already tried creating a fresh view, adding a new Process Explorer component from scratch, and reconnecting it to the same KM — same result. The issue follows the Knowledge Model, not the component or the view.

Anyone seen this before, or have an idea where to start looking?

Best answer by yingtao.gu13

One thing worth checking: Visual Mappings (color rules) in the Knowledge Model YAML. This came up as a potential cause in a similar situation and turned out to be the fix.

The way it seems to work: Visual Mappings reference a ruleGroup property in the KM via a referencedRuleGroupMetadataId. If one of those IDs points to a ruleGroup that no longer exists, it may break the Process Explorer specifically — other components like Variant Explorer apparently handle it more gracefully, which would explain the inconsistency you're seeing.

If that sounds plausible, it might be worth opening the KM YAML and checking whether any referencedRuleGroupMetadataId values under visualMappings have a matching entry in the ruleGroups section. Deleting any orphaned references would be the thing to try — going through them one by one is a bit tedious if there are many, but probably faster than deleting and recreating everything from scratch.

As for why it happens in the first place, that's less clear. One theory is that deleting certain components sometimes leaves behind references that don't get fully cleaned up, but that's more of an educated guess than anything confirmed.

      1 reply

      yingtao.gu13
      Level 8
      Forum|alt.badge.img+13
      • yingtao.gu13
      • Level 8
      • Answer
      • September 24, 2026

      One thing worth checking: Visual Mappings (color rules) in the Knowledge Model YAML. This came up as a potential cause in a similar situation and turned out to be the fix.

      The way it seems to work: Visual Mappings reference a ruleGroup property in the KM via a referencedRuleGroupMetadataId. If one of those IDs points to a ruleGroup that no longer exists, it may break the Process Explorer specifically — other components like Variant Explorer apparently handle it more gracefully, which would explain the inconsistency you're seeing.

      If that sounds plausible, it might be worth opening the KM YAML and checking whether any referencedRuleGroupMetadataId values under visualMappings have a matching entry in the ruleGroups section. Deleting any orphaned references would be the thing to try — going through them one by one is a bit tedious if there are many, but probably faster than deleting and recreating everything from scratch.

      As for why it happens in the first place, that's less clear. One theory is that deleting certain components sometimes leaves behind references that don't get fully cleaned up, but that's more of an educated guess than anything confirmed.

      Help companies to achieve digital process excellence
        Community Code of ConductAccessibility statement