Publishers use several different caching plugins to speed up their site. Sometimes this can create conflicts with out-of-date content or assets.
If something isn't behaving as expecting, a good place to start investigating are caching or performance plugins.
Here's a list of practices we'd recommend. (We'll keep this article up-to-date as issues are reported.)
Disable caching for logged-in users. Depending on your plugin of choice, this might setting be called something else. When you're logged in, having caching enabled can effect whether or not your changes are being correctly saved or seen by you.
If a card isn't updating on the front-end, purge the cache for the post. If that doesn't work, try republishing the card. We try to work with major caching plugins to purge caches whenever a card is published, but sometimes this doesn't work. Usually, purging a cache is enough to fix the issue. In some cases, however, the published card data is out of sync with the card data we automatically save as your editing. If this happens, clicking the "Publish" button will republish the card data (there's no need to update the blog post, in this case.)
Disable “Cache Rest API.” Anytime you’re using Create, you’re also taking advantage of the WordPress Rest API. Caching the Rest API can sometimes affect the functionality of Create, so if you’re using Litespeed and you notice any unexpected behavior from Create you can try disabling this setting.
WP External Links
This plugin is incompatible with Create. More accurately, conflicts between WP External Links and any plugin that uses a PHP technique called output buffering can indirectly cause issues with Create and other REST API functionality, including core WordPress.