Troubleshooting Shared Product States
One user sees a tenant and another does not
Check:
- whether both users belong to the same company scope
- whether one user has tag-limited or focused visibility
- whether the difference is role-based or visibility-based
The message row is visible, but payload content is not
Typical causes:
- payloads are intentionally restricted
- the user may see the object, but not the sensitive content
- the issue is permission-related, not necessarily a sync problem
An alert is acknowledged, but the problem still exists
That usually means ownership changed, not the technical cause.
Check:
- whether the condition is still active
- whether a newer alert row replaced the previous one
- whether you need message, artifact, or keystore context next
An archive row remains visible although the file is gone
That usually means historical metadata still exists while the downloadable content was already removed.
AI-supported output looks incomplete
Check:
- whether the underlying data is masked
- whether the current user is in a narrowed scope
- whether the visible context is sufficient for a confident interpretation
When to use the technical docs
Switch to /sysdocs when you need:
- exact role and permission enforcement
- value definitions from the underlying models
- AI and LLM operating constraints
- lifecycle and worker internals