I’ve enabled the extension but encountered the warning: Could not acquire lock for cron job: amasty_fpc_process_queue. How to resolve?
If the amasty_fpc_process_queue cronjob has Pending status, and you see this warning, it’s likely that the warming schedule needs to be adjusted. Such warnings generally occur when the extension tries to run the warming process when the previous one is still running. To resolve the issue, you may either decrease the single batch size or increase the step of the warmer schedule.
Related Articles
How can I know that the Full Page Cache Warmer extension is working?
To check whether the extension is working, you may generate the queue and start the warming process. After that, the links should start populating the warmer log. If the module works as expected, and the configuration is correct, the status will be ...How many pages the Full Page Cache Warmer extension warms per hour?
It is hard to provide the exact number of pages that the Full Page Cache Warmer extension can warm per hour as the warming speed fully depends on the server performance. However, you may get the approximate number of pages by dividing 3600 (an hour ...FPC Warmer logs allocate too much space in database. How to solve this?
Sometimes data in the amasty_fpc_activity table may pile up and take a lot of space. At the moment the extension lacks the functionality of auto-cleaning this log. Therefore, the solution is to manually clear the Customer Activity Log table. It is ...Does the Full Page Cache Warmer extension work with Fastly?
The Full Page Cache Warmer extension is compatible with Fastly CDN, since the core of Fastly is Varnish. However, keep in mind that the crawler is not able to identify whether the page is cached, as the cache is being stored in Fastly. As a result, ...While warming the pages, I see 0 in the Time column of the Warmer Log. Does it mean that the pages are not warmed?
After warming the pages, the Time column in the Warmer Log sometimes contains 0 value. However, it does not mean that the pages are not warmed. By default, the extension takes the CURRENT_TIMESTAMP value from the database, transforms it and rounds it ...
Announcements
⚡ Have you enlarged the functionality of the Amasty extension with your own code? Share your improvements with us!
At Amasty, we understand that some of our clients require customized features to perfectly align the extension with their business needs. If you have developed new functionality within an Amasty module and would like to share it, please submit a ticket