** Note that this is a public ticket, please refrain from adding any sensitive data. **

As per the Jira https://issues.redhat.com/browse/CHAINSAW-487 we understand, this change means that any registered system (consumer) that does not check in for 30 days will be automatically removed from the RHSM database. However, this behavior seems to differ from the system staleness and deletion settings on console.redhat.com, where:

• A system is marked "stale" after 1 day of no check-in (yellow icon),
• Further stale warning after 7 days (red icon),
• And automatically deleted after 14 days, though this can be customized by the user to extend deletion up to 2 years.

We'd appreciate clarification on how the Candlepin 30-day deletion interacts with the console.redhat.com system lifecycle settings, especially for customers using extended retention periods. Add details in the inventory documentation correctly that the  system staleness and deletion settings are primarily applicable to Satellite-managed systems and discovery reported systems, and do ** not apply to systems directly connected to RHSM OR RHSM + insights.   We will need to update the official documentation 

5.2. Modifying system staleness and deletion time limits in inventory 

Inactive system policy for Red Hat Subscription Management (RHSM)

https://access.redhat.com/articles/rhsm_inactive_system_policy

Document in product doc about the Hosted Candlepin's 30 day cleanup rule and how it affects the HBI's setting.