What it requires. A constraint model has not been synced since its products' definitions changed in Product Catalog Management.
Why it matters. [doc] Salesforce ships a sync mechanism because CML encodes product structure at authoring time: "Sync product definition changes from Product Catalog Management (PCM) to the constraint modeling language (CML)... to make sure that the CML reflects the latest product definition." The failure consequence - the configurator enforcing yesterday's product, valid configurations rejected and invalid accepted - is inferred from that mechanism and is stated as inference: Salesforce documents the sync, not the failure. The stale-tables mechanism at the configurator layer. Child-page pin outstanding; parent page cited.
How to fix it. Run the constraint model sync after product definition changes, and put the sync into the change process.
Source. Salesforce Help: Rules and Constraints in Configurator (sync section)
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.