When testing a communication, you might see that some content doesn't change as intended. Outdated content might include an image that won't change even though you just inserted a new image or a portal page that won't show the questions in a questionnaire you just configured.
Below, we've outlined a few of the common reasons why you might encounter outdated content and what you can do to troubleshoot it.
The common reasons why content might appear outdated are that:
- You didn't publish to Production
- Your browser shows a cached version of your content
- The recipient no longer matches the Conditions of the dynamic content block
You didn't publish to Production
Some content changes, such as changing an image, require that you publish to the Production environment to take full effect. Learn How to Publish to Production
Your browser shows a cached version of your content
A browser cache is a temporary storage location on your computer for files downloaded by your browser to display websites. This ensures that your computer doesn't have to download the same images and other content every single time you visit the same website.
However, this also means that you might see an outdated version of your Agillic instance which was saved by your browser cache. To check that your browser cache isn't the reason why you're seeing outdated content, clear your browser's cache and refresh the page.
The recipient no longer matches the Conditions of the dynamic content block
When testing with a recipient, be cautious if your updated content is in a dynamic content block like a Promotion Block, Variant Group Block, One-to-many Table Block, and the like. If you're seeing outdated content, it might be because your test recipient doesn't meet the conditions needed to see the right variation of your Dynamic Content Block.
Ensure that your test recipient has the required data for the correct version or create a new test recipient with the accurate data. Learn about How to Insert Content Blocks in Agillic