.png)
What This Issue Means
A cluster node may start without schemas or show missing schema definitions.
This happens when HCMS cannot locate, create, or load the schema asset.
How Schema Storage Works
HCMS stores schemas in a censhare asset identified by a resource key.
For schema loading to work, the asset must:
-
be unique,
-
exist in censhare,
-
contain the correct output channel.
If any of these are missing → HCMS treats the schema as unavailable.
Why a Node Can “Lose” Its Schema
A node may appear to lose schemas after restart when:
-
the resource key already exists and conflicts with another asset,
-
the existing asset does not have the correct output channel,
-
schema creation failed (asynchronous write failure),
-
schemas existed only in memory but not in a valid asset
After restart → HCMS reloads → cannot find a valid schema asset → schemas appear “lost.”
Manual Installation Makes This More Frequent
This issue happens more often when HCMS is installed manually because:
-
the partner must choose the resource key themselves,
-
generic keys like "schemas" are commonly used,
-
the chance of conflict becomes very high.
The hcms CLI tool avoids this by:
-
generating a unique resource key automatically,
-
greatly reducing conflicts in clustered environments.
What to Check
When schema loading fails:
-
Check that the resource key is unique.
-
Confirm whether an asset with the same key already exists.
-
Verify that the schema asset has the correct output channel.
-
Review startup logs for schema creation/update failures.
-
If installed manually → replace the generic resource key with a unique one
What Support Needs
To troubleshoot, provide:
-
HCMS configuration XML,
-
startup logs,
-
the resource key used,
-
output channel configuration.
(Logs are required; configuration alone is not enough.)
Summary
Schema‑loading issues in clusters usually stem from resource key conflicts or missing output channels.
These problems happen more often in manual installations because non‑unique resource keys are frequently used.
Using the hcms CLI tool is recommended since it generates unique, conflict‑free keys by default.