Title: Default cache timeout
Last modified: February 6, 2019

---

# Default cache timeout

 *  Resolved [dmsims](https://wordpress.org/support/users/dmsims/)
 * (@dmsims)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/default-cache-timeout-2/)
 * The default timeout for the plugin is 136 hours
 * This causes pages with a Caldera contact form to fail with a message:
 * Error: Submission rejected, token invalid
 * Setting the Litespeed cache timeout to 36000 seconds (10 hours) resolves this
   issue
 * [https://calderaforms.com/doc/caldera-forms-submission-rejected-token-invalid-mean/](https://calderaforms.com/doc/caldera-forms-submission-rejected-token-invalid-mean/)
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fdefault-cache-timeout-2%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Support [Hai Zheng⚡](https://wordpress.org/support/users/hailite/)
 * (@hailite)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/default-cache-timeout-2/#post-11176467)
 * We have an exclusive feature ESI to solve this compatibility issue perfectly.
 * Please take a look at [https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscwp:esi_replace](https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscwp:esi_replace)
 * Basically, to make token still valid, it is possible to keep cache TTL as long
   as you want, even 1 year. Just punch a hole for that token and make its TTL 10
   hours only.
 *  Plugin Support [Hai Zheng⚡](https://wordpress.org/support/users/hailite/)
 * (@hailite)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/default-cache-timeout-2/#post-11176500)
 * If you are using shortcode, an easier way is to try making it an ESI shortcode.
 * Here is the wiki: [https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscwp:configuration:esi:shortcode](https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscwp:configuration:esi:shortcode)
 *  Thread Starter [dmsims](https://wordpress.org/support/users/dmsims/)
 * (@dmsims)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/default-cache-timeout-2/#post-11176531)
 * Thanks for the replies
 * I don’t think the first solution is sustainable: if Caldera do a plugin update
   the changes could be overwritten
 * Will take a look at the shortcode
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/default-cache-timeout-2/#post-11224667)
 * Hi,
 * How is your shortcode test ?
 * from github history , caldera is already compatible with LSCWP since 1.5.6.2
 * Have you enabled ESI ?
 * Best regards,
 *  Thread Starter [dmsims](https://wordpress.org/support/users/dmsims/)
 * (@dmsims)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/default-cache-timeout-2/#post-11254795)
 * Okay so slightly confused at this point!
 * Changing the global cache timeout did not work, I had to deactivate the plugin
 * With ESI
 * is it just a question of enabling it in the plugin options or do you have to 
   use the shortcode as well ?
 *  Plugin Support [Hai Zheng⚡](https://wordpress.org/support/users/hailite/)
 * (@hailite)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/default-cache-timeout-2/#post-11254856)
 * Caldera Form has our ESI API embedded. For the nonce it will automatically generate
   a separate cache. If you have ESI turned on, it will use your `Default Private
   Cache TTL` setting for that nonce caching. By default `Default Private Cache 
   TTL` is 1800, it won’t get expired.
 * For most other plugins, [@qtwrk](https://wordpress.org/support/users/qtwrk/)’
   s answer (ESI shortcode) is a general approach to fix the timeout issue. For 
   Caldera Form, it’s not needed.
 * Also, we currently improved the compatibility with Caldera Form in Gutenberg.
   If you are using WP5, you may want to give it ([https://github.com/litespeedtech/lscache_wp/archive/master.zip](https://github.com/litespeedtech/lscache_wp/archive/master.zip))
   a try or wait for LSCWP v2.9.4 release.
 * Please share a report number if you still have this issue.

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

The topic ‘Default cache timeout’ is closed to new replies.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

 * 6 replies
 * 3 participants
 * Last reply from: [Hai Zheng⚡](https://wordpress.org/support/users/hailite/)
 * Last activity: [7 years, 2 months ago](https://wordpress.org/support/topic/default-cache-timeout-2/#post-11254856)
 * Status: resolved