QuestionQ40

VerifiedTroubleshoot infrastructure and configuration issues

An Adobe Commerce Architect is investigating an issue on an Adobe Commerce Cloud project that has not gone live yet.

Developers copied the Staging Database to Production in preparation for Go Live. However, when they test the Product Import feature, the new products are not visible on the front end.

The developers believe the Varnish Cache is not being cleared. Staging appears to work as expected, and Production worked before the database migration.

What is the most likely cause?

Explanation

Adobe Commerce Cloud assigns distinct Fastly Service ID and API token credentials to Staging and Production. Copying the Staging database to Production can replace the Production Fastly configuration with Staging credentials. Fastly invalidation then targets the wrong environment, leaving stale content on the Production frontend.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!