Troubleshooting item validation failed errors caused by mismatched item restrictions

If a purchase or delivery attempt fails with an error like item validation failed for SKU '...', one possible cause is that the item's restriction settings do not match between the Aghanim Hub configuration and the internal game-side configuration or database.

Symptoms

• The transaction is created, but item delivery fails.
• The API or logs show an item validation failed message for a specific SKU.

Possible cause

The SKU exists, but one of its validation parameters differs between systems. In the reviewed case, the root cause was a mismatch in the item's level restriction between the Hub and the internal database.

Resolution

1. Open the affected SKU in the Hub.
2. Compare its restriction settings against the game-side or internal database configuration.
3. Correct any mismatched values, including level-gating rules.
4. After the configuration is aligned, review already affected purchases separately. If players successfully paid but did not receive the item, those entitlements may need to be granted manually or otherwise remediated based on your integration flow.

Notes

• Aghanim item settings may require manual updates when game-side configuration changes.
• If the SKU value itself is correct, also verify all validation-related fields, not just the SKU identifier.
• Some integrations do not automatically retry failed item grants, so fixing the configuration alone may not resolve previously failed deliveries.