Caching for Subscription details retrieval from Central

Fixed incorrect caching of subscription details from Central that caused store deployments to overload requests, by reducing the cache duration from 24 hours to 2 hours.

This includes:

• Reduced cache duration from 24 hours to 2 hours

• Forced cache setup to fix incorrect caching

How it benefits the Merchant

This prevents store deployments from overloading backend requests, reducing the risk of deployment slowdowns or failures caused by subscription data checks.

Potential FAQs

Q: Do I need to change any settings for this fix?

A: No action is needed — the cache duration change and fix apply automatically.

Q: Will this affect how quickly subscription changes take effect on my store?

A: With a shorter 2-hour cache duration, subscription detail changes should now be reflected sooner than under the previous 24-hour cache.