Judging by your admin screenshot, is there any reason you are using two FPCs? Lesti_FPC and Evolved Caching? Normally only one FPC is needed, and judging by Evolved caching documents it has more support for things like Varnish, etc. compared to Lesti_FPC.

Basically you are doubling the work of the caching mechanisms and over complicating caching by having two FPCs you are having to manage for expiration and hole punching.

Normally the below XML layout on your static blocks will handle the hole punching:

<reference name="myblock"><action method="unsCacheLifetime"></action></reference>

But this also depends if the FPCs you are using rely on Magento Blocks caching for hole punching and entire page expiration. I would recommend disabling one of the FPC's you are using and refer to the documentation on the one planning on leaving in place in regards to hole punching a dynamically created block.

You can also specify each of the usual cache details for each block:

{{block type="core/template"
        template="template/category-block.phtml"
        block_id="my-block"
        cache_lifetime=0 
        cache_tags="CACHE_TAG_MY_BLOCK"
        cache_key="my-block"}}

More details:

• http://magento.stackexchange.com/a/105136/69
• http://blog.husseycoding.co.uk/2013/02/evolved-caching-magento-extension_18.html
• http://magento.stackexchange.com/a/13992/69

You can also use AOE_TemplateHints to help identify blocks and see the caching details of each block in question: https://github.com/fbrnc/Aoe_TemplateHints

Judging by your admin screenshot, is there any reason you are using two FPCs? Lesti_FPC and Evolved Caching? Normally only one FPC is needed, and judging by Evolved caching documents it has more support for things like Varnish, etc. compared to Lesti_FPC.

Basically you are doubling the work of the caching mechanisms and over complicating caching by having two FPCs you are having to manage for expiration and hole punching.

Normally the below XML layout on your static blocks will handle the hole punching:

<reference name="myblock"><action method="unsCacheLifetime"></action></reference>

But this also depends if the FPCs you are using rely on Magento Blocks caching for hole punching and entire page expiration. I would recommend disabling one of the FPC's you are using and refer to the documentation on the one planning on leaving in place in regards to hole punching a dynamically created block.

You can also specify each of the usual cache details for each block:

{{block type="core/template"
        template="template/category-block.phtml"
        block_id="my-block"
        cache_lifetime=0 
        cache_tags="CACHE_TAG_MY_BLOCK"
        cache_key="my-block"}}

More details:

• https://magento.stackexchange.com/a/105136/69
• http://blog.husseycoding.co.uk/2013/02/evolved-caching-magento-extension_18.html
• https://magento.stackexchange.com/a/13992/69

You can also use AOE_TemplateHints to help identify blocks and see the caching details of each block in question: https://github.com/fbrnc/Aoe_TemplateHints