Title: Timeout error 524 when doing cron
Last modified: September 26, 2020

---

# Timeout error 524 when doing cron

 *  Resolved [rcostabranco](https://wordpress.org/support/users/rcostabranco/)
 * (@rcostabranco)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/timeout-error-524-when-doing-cron/)
 * Hi, first of all, congratulations on your plugin.
    It’s really, really good! 
   I have installed it on many sites, and it is perfect!
 * However, in a woo online store, which imports products via an external server,
   I am having the following problem:
 * 1. When using your plugin, a cronjob that makes a connection to an external server
   to import products for woocommerce, is always interrupted after 4 or 5 minutes
   of activity
    2. It gives timeout error 524 3. If I disable your plugin, this 
   cronjob works correctly 4. It also works with the cloudflare proxy (orange cloud)
   enabled. And with 99% certainty, it also works with the “cache everything” page
   rule enabled. The error only happens with your plugin enabled (and cache enabled).
   5. I did several tests and modifications to the plugin options, but without success.
   6. I also created exceptions for bypass (both in the plugin and directly in the
   cloudflare page rules), urls like: »Domain.com/wp-cron.php* »Domain.com/*doing_wp_cron
   =* But without success. 7. The cron system we use is the default wordpress 8.
   Your plugin is installed with the latest version. 9. Server is VPS, NGINX, PHP
   7.4.
 * Could you help me, please?
 * Thank you very much.

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Contributor [Salvatore Fresta](https://wordpress.org/support/users/salvatorefresta/)
 * (@salvatorefresta)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/timeout-error-524-when-doing-cron/#post-13457431)
 * Hi [@rcostabranco](https://wordpress.org/support/users/rcostabranco/) ,
    strange.
   Something on log file while cronjob is executed?
 *  Thread Starter [rcostabranco](https://wordpress.org/support/users/rcostabranco/)
 * (@rcostabranco)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/timeout-error-524-when-doing-cron/#post-13463500)
 * Hi [@salvatorefresta](https://wordpress.org/support/users/salvatorefresta/),
 * Sorry for my late reply.
 * After further testing and looking more closely at the log, I saw / confirmed 
   that every time a new product was inserted a purge was made by your plugin.
    
   So, although the day before I thought I had already done this test, the truth
   is that everything started to work well, after disabling this option: Automatically“
   Purge cache for related pages only – (recommended)”.
 * Now we have another problem, which is to create a cron event to purge the cache.
   The defined URL returns false when running the cron job. The URL was copied from
   the “Other” tab:
    [https://domain.com/?swcfpc=1&swcfpc-purge-all=1&swcfpc-sec-key=123456789abc](https://domain.com/?swcfpc=1&swcfpc-purge-all=1&swcfpc-sec-key=123456789abc)
 * Could you provide me with the code that should be used to access the page via
   cron job?
 * Thank you very much.
 *  Plugin Contributor [Salvatore Fresta](https://wordpress.org/support/users/salvatorefresta/)
 * (@salvatorefresta)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/timeout-error-524-when-doing-cron/#post-13467004)
 * Hi [@rcostabranco](https://wordpress.org/support/users/rcostabranco/) ,
    you 
   are right. I fixed the error. Wait the upcoming release but as workaround you
   can use the following URL:
 * [https://domain.com/?swcfpc=1&swcfpc-purge-all=123456789abc](https://domain.com/?swcfpc=1&swcfpc-purge-all=123456789abc)
 * (as workaround, the value of swcfpc-purge-all must be the one of swcfpc-sec-key)
 * but don’t forget to change this URL with the original one when you update to 
   4.3.7
 *  Thread Starter [rcostabranco](https://wordpress.org/support/users/rcostabranco/)
 * (@rcostabranco)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/timeout-error-524-when-doing-cron/#post-13469028)
 * Hi [@salvatorefresta](https://wordpress.org/support/users/salvatorefresta/) ,
 * I appreciate the workaround and the fact that you will correct this in the next
   version. However, this workaround continues to give the same error, it returns
   false…
    Thank you.
 *  Plugin Contributor [Salvatore Fresta](https://wordpress.org/support/users/salvatorefresta/)
 * (@salvatorefresta)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/timeout-error-524-when-doing-cron/#post-13470012)
 * Hi [@rcostabranco](https://wordpress.org/support/users/rcostabranco/) ,
    can 
   you please send me via email the real URL?
 *  Thread Starter [rcostabranco](https://wordpress.org/support/users/rcostabranco/)
 * (@rcostabranco)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/timeout-error-524-when-doing-cron/#post-13470090)
 * Sent, [@salvatorefresta](https://wordpress.org/support/users/salvatorefresta/).
   
   Thank you for your support and congratulations on your plugin once again.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Timeout error 524 when doing cron’ is closed to new replies.

 * ![](https://ps.w.org/wp-cloudflare-page-cache/assets/icon-256x256.gif?rev=3234997)
 * [Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals](https://wordpress.org/plugins/wp-cloudflare-page-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-cloudflare-page-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [rcostabranco](https://wordpress.org/support/users/rcostabranco/)
 * Last activity: [5 years, 8 months ago](https://wordpress.org/support/topic/timeout-error-524-when-doing-cron/#post-13470090)
 * Status: resolved