I’ve enabled the extension but encountered the warning: Could not acquire lock for cron job: amasty_fpc_process_queue. How to resolve?

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 to Configure the FPC Warmer Extension?

        To ensure the FPC Warmer extension automatically warms pages on your website, you need to set up a valid warming schedule. Follow these steps for proper configuration: 1. Set the Queue Max Size First, estimate how many pages should be warmed based on ...

      • 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 in System > Amasty FPC Warmer > Warmer Queue. After that, the links should start populating the warmer log at in System > Amasty FPC Warmer > Warmer ...

      • Does Full Page Cache Warmer work with a Load Balancer?

        The Full Page Cache Warmer extension does not explicitly cache any pages. Instead, it crawls the pages with certain parameters and triggers the existing Magento caching mechanisms (Built-In cache, Varnish, Fastly, etc.) to cache these pages. ...

      • 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, which can cause certain performance issues on your website. To prevent this, it is recommended to regularly clear the Activity Log. You can do this manually or set ...